The Timeless 9 Golden Rules of Debugging

Re:The Timeless 9 Golden Rules of Debugging by gregthelaw on Monday January 13, 2025 @03:59PM (#42689210)

But if you don't squash, doesn't this render git bisect almost useless?

I think every commit that gets merged to main should be an atomic believed-to-work thing. Not only does this make bisect way more effective, but it's a much better narrative for others to read. You should write code to be as readable by others as possible, and your git history likewise.

[ Parent | on HN ]

Re:The Timeless 9 Golden Rules of Debugging by Izkata on Monday January 13, 2025 @06:08PM (#42690799)

Individual atomic working commits don't necessarily make a full feature. Most of the time I build features up in stages and each commit works on its own, even without completing the feature in question.

[ Parent | on HN ]

Re:The Timeless 9 Golden Rules of Debugging by forrestthewoods on Monday January 13, 2025 @06:14PM (#42690870)

You should read my original comment.

git bisect should operate on bisectable commits. Which may not be all commits. Git is missing information. This is, imho, a flaw in Git.

[ Parent | on HN ]

Re:The Timeless 9 Golden Rules of Debugging by badmintonbaseba on Tuesday January 14, 2025 @09:37AM (#42697693)

git bisect --first-parent

[ Parent | on HN ]