| 39 | Finding Bugs with bisect |
Unit tests, code review, pair programming, and any number of
practices help limit the number of bugs in your code. We all end
up having to track down bugs, though. It’s part of
software development. git bisect helps
you limit the time you spend on this unpleasant task by helping you
search through your repository’s history for the commit that
introduced the bug.
git bisect works by dividing and conquering. You know that a
particular commit has a bug in it, or is bad. You
also know that a particular point in the past didn’t have that bug
in it, or is good.
bisect takes the remaining commits, divides them in half, and sets your working tree to that midway point in the history. You can check your repository ...