2 ms·
By squashing, you lose ability to effectively bisect. Instead of finding an offending commit that has only a few lines to analyze, you only get a massive featu
by pornel 3y ago
By squashing, you lose ability to effectively bisect.
Instead of finding an offending commit that has only a few lines to analyze, you only get a massive feature-landing commit that doesn't narrow it down.
Interactive rebase or amend can be used to squash "oops forgot a semicolon" junk commits.
- thealistra 3y agoThis is literally furthest front the truth. Instead of having develop of all building test passing squashed commits you have to fiddle with bisect around commits that accidentally break the build and fail test and god knows why. Squash is basically a hard requirement for bisect to be useful at all. Especially for compiled languages.
- pornel 3y agoI think you're typically dealing with much messier git histories than I do. Anyway, accidentally-breaking commits can be skipped, but squashed commits can't be unsquashed.