Biset

Rationale

  • Find the commit that introduced the bug

    • Between a known good version and

    • a known bugged version

  • It will move to the mid-point iteratively until you find the commit and mark it.

  • You will do the test to tell whether there's a bug

Command

  • git bisect start: start

  • git bisect bad [<commit>]: mark the commit as bad, if no commit provided, it will use the current one.

  • git bisect good [<commit>]: similarly, mark as good

  • git bisect reset: exit, back to HEAD.

Last updated