Git bisect is a binary search. You tell it what the last known good revision is, and then it'll perform a binary search for you between that revision and the la

Git bisect is a binary search. You tell it what the last known good revision is, and then it'll perform a binary search for you between that revision and the latest revision. In each step of the binary search Git will ask you whether the current revision is good or bad, and in about O(log N) steps you'll know which exact revision introduced the regression. > (You may be surprised that Git leaves them around from previous versions) Git leaves directories around only if they contain files that are not checked in version control.