Menu
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 abort the entire bisect so that I can re-initiate the operation. git bisect reset seems to be what I am looking for, but I want to double check before potentially messing anything up.
923
git bisect reset is how you stop bisecting. By default it will reset the HEAD to where it was before you started, although you can also use git bisect reset <commit> to go to that one instead.
Use git log to check the previous commits. Use Git Bisect to find the commit in which line 2 is changed from 'b = 20' to 'b = 0.00000'. Remove the bad commit by using Git Revert. Leave the commit message as is.
git bisect reset is the correct command. From the documentation:
After a bisect session, to clean up the bisection state and return to the original HEAD, issue the following command:
$ git bisect resetBy default, this will return your tree to the commit that was checked out before
git bisect start. (A newgit bisect startwill also do that, as it cleans up the old bisection state.)
71
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
