1 link tagged with all of: refactoring + squash-merge + commits
Click any tag below to further narrow down your results
Links
The author argues for splitting mechanical and “real” changes into separate, even temporarily broken, commits to make code reviews simpler. By using squash-and-merge, you get a clean long-term history while reviewing a step-by-step narrative that’s easier to validate.