finding-bug-commits

What I do

• Guide you through using git bisect to find bug-introducing commits
• Help you choose between automated (script-based) or manual bisect approaches
• Provide step-by-step workflows with progress tracking
• Handle edge cases like untestable commits and bisect recovery

Choosing the approach

Use automated bisect when:

• The bug is reproducible with a command (build, test, script)
• Testing doesn't require human judgment
• You can script the pass/fail detection

Use manual bisect when:

• The bug requires visual inspection or UX judgment
• Testing involves complex setup or interaction
• The reproduction steps can't be easily scripted

Automated bisect workflow