Re:Fortunately, I don't squash my commits
by hawkice on Monday October 05, 2020 @02:16PM
(#24690395)
I think you're missing out on the main advantage the article points out: lots of small commits, even with terrible error messages, let you use tools like git bisect to find bugs. Squashed commits mean you're looking through more code, and above some small size, it won't be obvious what the issue is.
[ Parent
| on HN ]
Bisects only work if every intermediate commit is a working state.
Re:Fortunately, I don't squash my commits
by windsurfer on Monday October 05, 2020 @03:23PM
(#24691070)
If what you're looking for is a specific breakage or result that doesn't depend on something "working", then each commit does not necessarily need to be working. You may also want to read about the git-bisect feature "old/new" which could help if you're just looking for a change and not a breakage.
Re:Fortunately, I don't squash my commits
by outworlder on Monday October 05, 2020 @02:43PM
(#24690662)
More often than not, lots of small commits, with incomplete changes, will make git bisect completely useless.
It takes someone that's, at the same time, making 'messy' commits with horrible messages, but also diligent enough to never commit any breaking changes.
Re:Fortunately, I don't squash my commits
by elgaard on Monday October 05, 2020 @07:38PM
(#24693276)
Not really.
With git bisect you know what you are looking for.
So even if you did make a commit with e.g., a missing semicolon you can still call it "good" because it did not cause the problem your are trying to debug.