Linux Shell Scripting Cookbook - Third Edition

How to do it...

The git bisect command requires two identifiers, one for the last known good code and one for the bad release. The bisect command will identify a revision midway between the good and bad for you to test.

After you test the code, you reset the good or bad pointer. If the test worked, reset the good pointer, if the test failed, reset the bad pointer.

Git will then check out a new snapshot midway between the new good and bad locations:

    # Pull the current (buggy) code into a git repository
    $ git checkout buggyBranch

    # Initialize git bisect.
    $ git bisect start

    # Mark the current commit as bad
    $ git bisect bad

    # Mark the last known good release tag
    # Git pulls a commit at the midpoint for testing.

 $ git bisect good v2.5 ...