Ever had a problem come up somewhere within a chain of commits, and you’re not sure which change caused the problem? Up to now, we’ve usually addressed this by doing a binary search between the last commit and the latest commit we can find where the problem hasn’t yet been introduced. I consider myself fairly experienced with Git, but I had no idea that it would do it for you!
The git bisect command is your friend in this case. An excellent blog post explaining how to use it can be found here: