Hosting Operations
Map Recent Release Commits
You need to see which tagged release commits exist before choosing a rollback target.
Command
cd /lab/git-recovery-rollback && git log --oneline --decorate --graph --all -8
What changed
Nothing changes. Git prints the recent commit graph with tags.
Danger
safe
When to use it
Use during rollback planning when you need the shape of recent releases quickly.
When not to use it
Do not rely on commit order alone when your deploy system can point at a different artifact or symlink.
Undo or recovery
No undo needed because this command is read-only.
Expected output
A compact commit graph showing release-2026-06-25-1030 and earlier release tags.
demo script
Disposable terminal steps
cd /lab/git-recovery-rollback && git tag --list 'release-*' | sort -Vcd /lab/git-recovery-rollback && git log --oneline --decorate --graph --all -8
simulated output
What it looks like
::fixture-ready::
$ cd /lab/git-recovery-rollback && git tag --list 'release-*' | sort -V
release-2026-06-24-1700
release-2026-06-25-1000
release-2026-06-25-1030
::exit-code::0
$ cd /lab/git-recovery-rollback && git log --oneline --decorate --graph --all -8
* de583c6 (HEAD -> main, tag: release-2026-06-25-1030) Release 2026-06-25 10:30
* c15c7c6 (tag: release-2026-06-25-1000) Release 2026-06-25 10:00
* ddb9d51 (tag: release-2026-06-24-1700) Release 2026-06-24 17:00
::exit-code::0
YouTube Short
Map release history fast.
Show the recent graph with decorations. The tags tell you which commits are rollback candidates.
LinkedIn hook
A rollback is easier when the last few release tags are visible.
Question: What command do you use to find the rollback target commit?
experiments
A/B tests to run
Metric: completion_rate
A: A rollback target should be visible.
B: Do not choose rollback commits blind.