The backup tag covers the local case, and docs/cli.md says so. It does not cover the case where the graft was pushed and something turned out wrong afterwards — which is when people actually panic.
What this needs
A short section in docs/cli.md (or its own page) covering:
- Reverting the range with
git revert --no-commit <startSha>..HEAD, and why that is preferable to a force-push on a shared branch.
- What happens to the
Regraft-source trailer when you revert: the trailer is still in history, so the next status believes those commits are applied. Reverting the content does not undo the record. The fix is regraft apply --from <sha> to force the starting point back.
That second point is the one nobody guesses, and it is the reason this issue is worth writing rather than assuming people know.
The backup tag covers the local case, and
docs/cli.mdsays so. It does not cover the case where the graft was pushed and something turned out wrong afterwards — which is when people actually panic.What this needs
A short section in
docs/cli.md(or its own page) covering:git revert --no-commit <startSha>..HEAD, and why that is preferable to a force-push on a shared branch.Regraft-sourcetrailer when you revert: the trailer is still in history, so the nextstatusbelieves those commits are applied. Reverting the content does not undo the record. The fix isregraft apply --from <sha>to force the starting point back.That second point is the one nobody guesses, and it is the reason this issue is worth writing rather than assuming people know.