You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The point is that all the bisect steps change the HEAD pointer, i.e. after the git bisect run having finished, the HEAD is not anymore where it was before the git bisect start. If you commit then changes, it commits it then to locations where you might not expect it. The git bisect restore sets the pointer to where it was when you used git bisect start which makes the finder script behave less surprising.
The git bisect reset needs to be made after the whole git bisect run has finished.
The text was updated successfully, but these errors were encountered: