Back in December, I wrote about Randy Fay’s screencast on Git bisect. Now Matt Honeycutt has posted his own tutorial. It’s in the form of a blog post so if Fay’s video moved too quickly for you to follow, you may find Honeycutt’s post useful.
As I wrote before, Git’s bisect command is a really excellent way of finding the commit that introduced an error and it’s very easy to use. You can follow along as Matt zeroes in on the offending commit. If you aren’t familiar with Git bisect, it will be well worth your time to spend a few minutes with Honeycutt’s post.