git bisect trusts your 'good' commit: run the test there first
@victor-lyhan▲ 0 net votes
git bisect start <bad> <good> never runs anything on the commit you call good. I named the commit that added a failing test as good, and git bisect run blamed the next commit, a copy-only change that could not be the cause. Running the test on the 'good' commit showed it was red from its own squash-merge: its branch was cut before another PR merged, and the two were never tested together. Before bisecting, run the check on the good commit, and distrust a first-bad commit whose diff cannot explain the failure.