Gitflow
🕵️‍♂️Blame + Bisect CombinedHard+750 XP
Workshop
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 · 5 steps · +750 XP

What you will practice

This scenario walks through 5 steps, in order:

  1. 01Blame the suspect file
  2. 02Start bisecting
  3. 03Mark current bad
  4. 04Show the culprit when found
  5. 05Finish 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. Start bisecting
    git bisect start HEAD bb00001
  3. 3. Mark current bad
    git bisect bad
  4. 4. Show the culprit when found
    git show bb00002
  5. 5. Finish bisect
    git bisect reset

Key takeaway

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

← Browse all scenarios