git bisect
Use binary search to find the commit that introduced a bug. Git automatically jumps back and forth in the commit graph to progressively narrow down the faulty commit. More information: https://git-scm.com/docs/git-bisect.
-
Start a bisect session on a commit range bounded by a known buggy commit, and a known clean (typically older) one:
git bisect start {{bad_commit}} {{good_commit}}
-
For each commit that
git bisect
selects, mark it as "bad" or "good" after testing it for the issue:
git bisect {{good|bad}}
-
After
git bisect
pinpoints the faulty commit, end the bisect session and return to the previous branch:
git bisect reset
-
Skip a commit during a bisect (e.g. one that fails the tests due to a different issue):
git bisect skip
-
Display a log of what has been done so far:
git bisect log
License and Disclaimer
The content on this page is copyright © 2014—present the tldr-pages team and contributors.This page is used with permission under Creative Commons Attribution 4.0 International License.
While we do attempt to make sure content is accurate, there isn't a warranty of any kind.