Undoing a git bisect mistake

git git-bisect
Graham Perks picture Graham Perks · Dec 21, 2011 · Viewed 12.3k times · Source

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

manojlds picture manojlds · Dec 21, 2011

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

Related questions

How to use git bisect?

I have read some articles saying that git bisect is awesome. However, I'm not a native speaker and I can't understand why it's awesome. Could someone please demonstrate with some code sample: How to use it? Is it just like …

Read More
Git bisect with merged commits

I have a history that looks like this: * 3830e61 Add data escaping. (Bad) * 0f5e148 Improve function for getting page template. * aaf8dc5 Merge branch 'navigation' |\ | * 3e667f8 Add icons. | * 43a07b1 Add menu styles. (Breaks) | * 107ca95 Add Responsive Nav. (…

Read More
How to Abort Git Bisect

I started my git bisect by specifying good and bad revisions but I don't think they registered. Additionally, as I am attempting to specify git bisect good and bad, I don't think git is doing anything. I would like to …

Read More