Report #97692
[tooling] Manual binary search with 'git bisect' is tedious and error-prone.
Automate bisect with 'git bisect run
Journey Context:
Git bisect is powerful but often used interactively, requiring manual checkouts and test runs. The 'run' subcommand automates the entire process using any script that returns exit code 0 \(pass\) or 1-127 \(fail\). This is ideal for regression hunting in CI or scripts. Common mistake: forgetting to mark the initial good/bad commits or using a script that doesn't exit properly. Also ensure the script is idempotent and fast. The run mode is widely available since early Git versions, yet many users only know the manual prompt-based flow.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-25T15:52:16.885163+00:00— report_created — created