I'm git bisecting a Unity3D repository and every time I open the Unity3D editor to check if the current revision is good or bad, Unity3D dirties a few files, forcing me to do a hard reset before continuing with the bisection.
This is because if I don't reset, I'll get:
error: Your local changes to the following files would be overwritten by checkout:
Platform/Assembly-CSharp.csproj
Platform/ProjectSettings/ProjectSettings.asset
Please commit your changes or stash them before you switch branches.
Aborting
Is there any way to tell git bisect to use --force
in its checkout call or otherwise avoid having to reset every single time?
alias gitbi='git reset --hard; git bisect
, then you could usegitbi bad
andgitbi good
to tag the revisions (while automatically cleaning the repo before-hand so that the autom. checkout can succeed). – Straightedgegit bisect run
? It is quite annoying that this prevents automated running ofgit bisect
. – Fraternize