Gitflow
🕵️‍♂️Blame + Bisect CombinedHard+750 XP
Scenario reference

Blame + Bisect Combined: the situation, step by step

The situation

A subtle UI bug appeared somewhere in the last 50 commits. Visual blame on the file gives 8 candidates. Bisect narrows it further.

Use blame to scope the file, bisect to pinpoint the commit, show to read it.

Hard · 7 steps · +750 XP

What you will practice

This scenario walks through 7 steps, in order:

  1. 01Blame the suspect file
  2. 02Name the oldest commit you know was fine
  3. 03Start bisecting
  4. 04Mark current bad
  5. 05Mark the old commit good — bisect checks out the midpoint
  6. 06Read the commit bisect handed you
  7. 07Finish bisect
Reveal the step-by-step commands

Try the terminal first — you learn more by doing. When you want to check yourself, here is the command for each step.

  1. 1. Blame the suspect file
    git blame src/ui/Modal.tsx
  2. 2. Name the oldest commit you know was fine
    git branch last-known-good HEAD~2
  3. 3. Start bisecting
    git bisect start
  4. 4. Mark current bad
    git bisect bad
  5. 5. Mark the old commit good — bisect checks out the midpoint
    git bisect good last-known-good
  6. 6. Read the commit bisect handed you
    git show HEAD
  7. 7. Finish bisect
    git bisect reset

Key takeaway

Blame to scope, bisect to bisect, show to confirm.

← Browse all scenarios