The Business of Bisecting
summary
Shows how to use git bisect to find the exact commit that introduced a regression, automating checks with a script or git bisect run so tests mark commits good with exit code 0 bad with nonzero and exit code 125 to skip untestable revisions. Demonstrates Dockerized runs, composer installs, a failing chog door demo, creating a regression test, bisecting to the first bad commit, then editing history via interactive rebase to add a fix and verify the test passes.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:48Git bisect basics
- 6:06Bisect workflow
- 9:21Bisect demo
- 11:53Advanced bisect use cases
- 13:40Custom bisect terms
- 15:25Fixing bisect mistakes
- 19:21Automating bisect
- 25:49Tests for regressions
- 26:12Real-world bisect example
- 36:19Small bisect scope
- 37:24Bisect skip untestable
- 40:34Skip with exit code 125
- 43:02Bisect scripting dependencies
- 47:26Creative bisect workarounds
- 48:29Bisect best practices
