Use Git bisect to find a regression
Use git bisect with an automated test script to binary-search through history and identify the exact commit that introduced a regression.
Preview
Copy prompt
Walk me through using git bisect to track down the commit that introduced [Bug description]. Start from: a known good commit at [Describe or give SHA] and the known bad commit at [Describe or give SHA]. Show the exact commands to start a bisect session, mark commits as good or bad, and interpret the binary search output at each step. Then show how to automate the entire bisect using `git bisect run` with a test script that exits with 0 for good and 1 for bad. Explain what to do with the result once the culprit commit is identified.
More
Git & Version Control
Prompts
