Gitflow
⏪Revert a Published ReleaseHard+700 XP
Workshop
Scenario reference

Revert a Published Release: the situation, step by step

The situation

You shipped v4.0 to production an hour ago. Customers are reporting checkout failures. main is public — you can't reset.

Revert (don't reset) public history. Tag the revert release as v4.0.1.

Hard · 3 steps · +700 XP

What you will practice

This scenario walks through 3 steps, in order:

  1. 01Revert the bad merge
  2. 02Tag the recovery release
  3. 03Push with tags
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. Revert the bad merge
    git revert -m 1 rp00002
  2. 2. Tag the recovery release
    git tag -a v4.0.1 -m "Revert v4.0"
  3. 3. Push with tags
    git push --follow-tags

Key takeaway

Reset rewrites history — never on public branches. Revert is additive and safe.

← Browse all scenarios