📁 Files

app.py

! ConflictS StagedM ModifiedU Untracked

No files staged. Use git add to stage changes.

📊 Commit Graphcurrent branchmain

🎯 Git BisectIntermediate0/7

📖 Concepts

git bisectA binary search tool to find which commit introduced a bug. You mark a known good commit and a known bad commit, and Git checks out the midpoint for you to test. Repeat until the first bad commit is pinpointed.

Bisect workflowStart with git bisect start, then mark git bisect good <ref> and git bisect bad <ref>. Git checks out a midpoint commit. Test it, then run git bisect good (no bug) or git bisect bad (bug present). Git halves the search each time. Finish with git bisect reset.

Bisect is diagnostic onlyBisect only finds the bad commit — it does nothing to fix it. It is purely a diagnostic tool. After git bisect reset, you are back where you started (HEAD unchanged, bug still present). The fixing is entirely up to you: • git revert <bad-commit> — safest option. Adds a new commit that undoes the bad one. Keeps history intact. • git reset --hard <good-commit> — nuclear option. Rewrites history by moving the branch pointer. Dangerous on shared branches. • Manually fix the code — just edit the file and commit the fix. The most common approach for small bugs.

View the commit history

Run git log --oneline. There are 5 commits. A bug was introduced somewhere. The last known good version is the initial commit (ba1b2c3). The current HEAD (be5f6g7) is broken — it has a "BUG" line in app.py.

● View the commit history

○ Start a bisect session

○ Mark the current commit as bad

○ Mark a known good commit

○ Test the midpoint and mark good

○ Test the next midpoint and mark bad

○ End the bisect session

Terminal

📘 Starting tutorial: Git Bisect

Find the commit that introduced a bug using binary search

Step 1: View the commit history