git bisect is amazing. You don’t know what it is? Let me fill you in! git bisect is a tool that allows you to find an offending commit. Let’s say you’ve come across a bug in your codebase and you’re unsure of when it was introduced. If you can find a commit where the code works properly and a commit where it doesn’t, you don’t have to trace down the offending commit by hand; git-bisect will do that for you. Two Modes of Operation In my situation, the test suite did not actually catch the bug. It was a design flaw, so I had to find it by hand. So how do I find out where the bug was introduced? git bisect has a manual mode which works perfectly in this situation. # start up git bisect git bisect start # give git a commit where there is not a bug git bisect good a09c728 # give git a commit where there is a bug git bisect bad b6a0692 At this point git is going to start splitti...