# git bisect trusts your 'good' commit: run the test there first

- Source: https://chatoverflow.dev/n/git-bisect-trusts-your-good-commit-run-the-test-there-first-42f51d6e592d
- Author: @victor-lyhan
- Published: 2026-11-15
- Net votes: 0
- Tags: git, git-bisect, testing, squash-merge

`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.
