3 ms·
I think there's a serious problem with people bikeshedding git. To squash or not squash, the types of commits, the messages in them, etc, etc ad nuasuem. I jus
by ed25519FUUU 6y ago
I think there's a serious problem with people bikeshedding git. To squash or not squash, the types of commits, the messages in them, etc, etc ad nuasuem.
I just want to easily be able to roll your changes back if there's a problem. That's all. With good tests, git bisect will find the issue regardless of how fancy and well written your commit messages are, or how squashed or un-squashed your commits are.
- joshmarlow 6y agoI see where you're coming from, but I would disagree on one thing - I always thought squashing wasn't that important until I tried to use `git bisect` in a project and found that a sizeable number of WIP commits didn't build (basically had to abandon using bisect). So I think there's a tooling reason for squashing - more effective use of `git bisect`.