Sometimes you find a bug in your project that has been around for a while without being noticed; it can be hard to track down where that bug was introduced and why just by searching through logs and diffs. Git has a slick tool called
git bisect that can be used to find out which commit introduced problem in our code - it creates a binary search where the programmer can mark each search commit as
bad; by the end of the bisect, Git shows you exactly which commit introduced the issue. In this lesson, we walk through an example of using
git bisect from start to finish.