Summary - Bisect

Combine the bisect flow to find the buggy commit.

Summary: Bisect workflow

To find which commit introduced a bug, start with git bisect start. Mark the faulty revision as bad and a working revision as good. Git narrows the range using binary search and selects a new commit at each step.

git bisect start
git bisect bad HEAD
git bisect good v1.0.0

You can inspect each commit manually or automate testing with git bisect run.

Exercise Find the faulty commit automatically

Start a bisect session. Mark the current commit as bad and the v1.5.0 tag as a working revision. Then run ./check-bug.sh automatically and reset the session when the search is complete.

Show example solution

git bisect start
git bisect bad HEAD
git bisect good v1.5.0
git bisect run ./check-bug.sh
git bisect reset

Test yourself

Git has identified the commit where the bug began. Which command ends the bisect session and returns to the previous branch state?
- git bisect good
- git bisect reset
- git bisect run
- git bisect bad
Show answer

git bisect reset — git bisect reset ends the bisect session and returns to the original HEAD position.

Automated search and testing

git bisect ____

Show answer

git bisect run ./check-bug.sh

Roles of bisect commands

git bisect start

Starts the search session
git bisect good

Marks a working commit
git bisect bad

Marks a faulty commit
git bisect run

Runs the test automatically

Next lesson: git blame

We Are Enhancing Your Experience

Cookie Preferences

Strictly Necessary Cookies

Analytical Cookies