In this lesson we're going to use the `git bisect` command to do a little bit of debugging. We're all human, and sometimes bugs get introduced our software and we may not notice them for a while. Especially on fast moving projects. A good example of this would be a performance regression, and now you want to figure out what commit made everything run slower all of a sudden. Bisect allows us to do a binary search between a known good commit and a known bad commit and quickly narrow down which commit introducted the problem. From there it's much easier to figure out what exactly the problem is and fix it.
Using Git Bisect