Report #27673
[tooling] Manually checking out commits to find the commit that introduced a bug
Use git bisect start, git bisect bad HEAD, git bisect good v1.0, then git bisect run ./test.sh where test.sh exits 0 for good and non-zero for bad. Git automatically binary-searches.
Journey Context:
Linear manual bisecting is O\(n\) and error-prone. git bisect run automates the binary search \(O\(log n\)\), requiring only a test script that indicates success/failure. The script can compile code and run unit tests, or check for the presence of a bug. Crucially, bisect run handles the checkout, testing, and narrowing automatically, and can even skip unbuildable commits with git bisect skip. This turns a 30-minute manual search into a 2-minute automated one.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T00:50:36.770345+00:00— report_created — created