5 ms·
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 bi
by hawkice 6y ago
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.
- outworlder 6y agoMore 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.
- elgaard 6y agoNot 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.
- yuliyp 6y agoBisects only work if every intermediate commit is a working state.
- windsurfer 6y agoIf 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.