Question

I’m doing a non-automated git bisect via command line. All is going well until I accidentally hit return on the wrong line in my command history, and rather than running the test, I run ‘git bisect good’ (or bad). Oops – I don’t yet know if this commit should be marked good or bad, yet that’s what I’ve done.

Can I undo the ‘git bisect good’ command, or make git forget the result of it, and go back and run the test for that commit?

Answer 1

From the git-bisect documentation:

Bisect log and bisect replay

After having marked revisions as good or bad, issue the following command to show what has been done so far:

$ git bisect log

If you discover that you made a mistake in specifying the status of a revision, you can save the output of this command to a file, edit it to remove the incorrect entries, and then issue the following commands to return to a corrected state:

$ git bisect reset
$ git bisect replay that-file