The git undo generator: three questions in, one command out

■ the answer first

Three questions — pushed or not, keep or discard, shared or solo — one exact command out, no account, all in the browser.

Pushed and others pull the branch? Revert is the only polite undo.

Committed and lost? Reflog rescue — dropped commits stay reachable ~90 days.

18states on the panel

4commands cover the mess

~90days the rescue stays open

01THE SORTER, LIVE

eighteen states queue in the hopper — keys 1 · 2 · 3 throw the levers, the drum sorts the ticket

FIG 1 · THE UNDO SORTERkeys 1 · 2 · 3 — or the buttons

WHERE PUSHED · ROUTED REVERT · VERDICT THE ONLY POLITE UNDO · RESETS REFUSED

the situation is "pushed to a shared branch" — the only command it offers is revert, because the alternatives burn teams.

18 states on the panel — three questions, 3 × 3 × 2 — and most collapse into the same handful of commands.

the REFUSED gantry is bolted across the three reset chutes — permanent structure, not a lever: pushed commits cannot enter

02THE DECISION TABLE

the sorter's whole brain, printed — the machine runs this lookup cell for cell, no account, nothing uploaded

Command	History	Working tree	Shared branch?
`git reset --soft HEAD~1`	moves back 1	changes kept, staged	no — rewrite
`git reset HEAD~1`	moves back 1	changes kept, unstaged	no — rewrite
`git reset --hard HEAD~1`	moves back 1	changes discarded	no — destructive
`git revert HEAD`	adds an undo commit	untouched	yes — the safe move
`git reflog` + `git switch -c recovery <sha>`	nothing lost	restored from reflog	rescue after anything

The shared-branch question is the whole tool. Everything else is convenience; that one is damage control.

03THE COMMANDS IT PRINTS

four commands cover almost every mess — copy the block, warning comments included

committed, not pushed — the local rewrites

# committed, not pushed, keep the changes staged
git reset --soft HEAD~1

# committed, not pushed, keep the changes unstaged
git reset HEAD~1

pushed — the only polite undo

# pushed, others pull this branch — the only polite undo
git revert --no-edit HEAD~1..HEAD
git push

committed and lost — the reflog rescue

# committed and lost — reflog knows for ~90 days
git reflog
git switch -c recovery <sha-from-the-list>

verify: git reset --soft HEAD~1 → changes kept, staged · git reflog + git switch -c recovery <sha> → nothing lost, restored from reflog

the range—HEAD~1..HEAD reverts exactly the commits you name — worth knowing even if the tool types it for you

the clock—the rescue only has something to rescue because git keeps dropped commits reachable roughly ~90 days

the phone test—one static page — no server, no analytics, no cookies — it loads in a server room, where git emergencies happen

04WHAT THE MACHINE REFUSES

the refusals are the feature — where the record declines to guess, the sorter prints the wall

shared branch—"pushed to a shared branch" offers one command: revert — the alternatives burn teams

own branch—the reset paths differ only in the force-with-lease tail — the tool still hands you the polite path first

no rebase help—reordering commits? you already know more than the tool teaches

no stash surgery—that has its own guide

the receipt—this site ranks for "git reset last commit keep changes" at position 12.3 — 27 impressions in one week, zero clicks — a query crying for a command, not an essay

source: github.com/mrsaynothing/git-undo — plain HTML and JavaScript, no build step, no dependencies. Fork it, restyle it, rip out my wording.

If it saves you one reflog session this year, it has paid for the afternoon it took.

■ honest stamp Tested on: git 2.4x command set · browser-only · no account, nothing uploaded. First published 2026-09-25. The decision table is the revert-vs-reset record turned into a lookup; every command prints as tested, warnings included. The tool is one static page of plain HTML and JavaScript — the only thing it sends anywhere is nothing.

end of the generator · nothing fetched · everything local