This feels too dogmatic to be very useful. I'll ofter a softer version that I think everyone can agree to? - Don't mix rewriting code and adding features in t

This feels too dogmatic to be very useful. I'll ofter a softer version that I think everyone can agree to? - Don't mix rewriting code and adding features in the same commits - If you're squashing commits on a feature branch, and there are rewrites in there, cherry-pick them to master and rebase That at least leaves you with the ability to track bugs down to rewrites vs. feature additions. The advice in the original post feels like it's potentially useful if it's in a large system that sees heavy use with good test coverage. Then it's probably the right impulse. But a lot of code isn't that.