I was tracking down a problem in my codebase with git bisect and I forgot to do a reset at the end. I'm now on another branch, in the middle of my work. What happens if I do it now? Do I need to wait until I'm done with this branch?
Asked
Active
Viewed 110 times
1
iconoclast
- 21,213
- 15
- 102
- 138
-
You mean, you starting adding changes to your code and now you don't know how to move them to where you actually need to work? – eftshift0 May 16 '19 at 21:30
-
@eftshift0: I don't understand exactly what you're describing, but I'm pretty sure that it's not what I'm asking. I'm asking how to exit the `git bisect` process non-destructively, since I forgot to do the `reset` when I was done bisecting and git still thinks I'm bisecting, and is waiting for a `git bisect reset`, at which time it will do stuff that I don't want it to do. I just want it to stop waiting for any `git bisect reset`. – iconoclast May 16 '19 at 23:35
1 Answers
3
It's as simple as tacking on HEAD (or any other commit) on the end, to avoid going back to the commit you were on before bisecting:
git bisect reset HEAD
iconoclast
- 21,213
- 15
- 102
- 138