hello all,

it would be super convenient if git bisect was able to flip-flop between 2 (or more) worktrees while bisecting.

This would leave both A, B in re-test-able states, allowing detailed forensics on the differences.

if this were a well-known feature, I could imagine that tools like rr would be enhanced to exploit it, due to the lure of a tightly controlled A-B test environment, maybe even doing side by side record & replay to find where things go differently.

and perhaps:

git bisect try <commit>   # go with a hunch

this would check out the commit, then testing would determine good/bad sort of the opposite of skip.

git bisect try HEAD~20 bad [ HEAD ]

here bisect doesnt pick the next, it follows your hunch

thanks for your consideration, ~jimc