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 docs explain how to use every-ts bisect run to find the commit that broke something, but sometimes you want to find the commit that fixed an issue.
Case in point: I tried to repro #33191 at HEAD today and couldn't. It was fixed sometime after 5.3.2.
I wound up doing it with this script that flips the exit codes. But maybe there's a better way that doesn't require that.
I was aiming not to do write too much on this, under the assumption that I would effectively just repeating the git bisect docs linked in the README.
I wound up doing it with this script that flips the exit codes. But maybe there's a better way that doesn't require that.
My example in the README actually uses the terms old and new for that reason. Though, I see now that I accidentally flipped the example, so I'll fix that quick.
The docs explain how to use
every-ts bisect run
to find the commit that broke something, but sometimes you want to find the commit that fixed an issue.Case in point: I tried to repro #33191 at
HEAD
today and couldn't. It was fixed sometime after 5.3.2.I wound up doing it with this script that flips the exit codes. But maybe there's a better way that doesn't require that.
The text was updated successfully, but these errors were encountered: