Back to lessons

Hosting Operations

Risk: safe

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

Before you run this

Risk: safe. Do not rely on commit order alone when your deploy system can point at a different artifact or symlink.

Expected output

A compact commit graph showing release-2026-06-25-1030 and earlier release tags.

System impact

Nothing changes. Git prints the recent commit graph with tags.

Recovery / rollback: no state is changed.

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.

Watch this command run

Example output from a temporary Linux lab

This example uses disposable sample files and sanitized output so you can inspect the shape of the result before touching a real system.

demo@lab:~$

$ cd /work/git-recovery-rollback && git tag --list 'release-*' | sort -V

release-2026-06-24-1700
release-2026-06-25-1000
release-2026-06-25-1030

$ cd /work/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
View reproducible demo details

This page shows the sanitized shell transcript and the setup steps needed to reproduce the example.

Lab setup steps

  1. cd /lab/git-recovery-rollback && git tag --list 'release-*' | sort -V
  2. cd /lab/git-recovery-rollback && git log --oneline --decorate --graph --all -8

next steps

Related commands

Hosting Operations Risk: caution

Revert the Suspect Release Commit

Undo a bad release with a new commit instead of rewriting history.

cd /lab/git-recovery-rollback && git restore -- app/config.yml && git revert --no-edit release-2026-06-25-1030
Hosting Operations Risk: safe

Preview the Patch a Rollback Would Apply

Show the exact file changes before moving the branch back.

cd /lab/git-recovery-rollback && git diff --stat HEAD..release-2026-06-25-1000
Hosting Operations Risk: safe

Find a Discarded Commit in Reflog

A reset does not mean the commit vanished.

cd /lab/git-recovery-rollback && git reflog --date=iso --format='%h %gd %gs' -6
Hosting Operations Risk: safe

Snapshot Git Status Before Recovery

Before rollback commands, capture the branch and dirty files.

cd /lab/git-recovery-rollback && git status --short --branch
Hosting Operations Risk: safe

Show Files Changed Since Last Good Release

Compare the suspect release against the last known-good tag.

cd /lab/git-recovery-rollback && git diff --name-status release-2026-06-25-1000..HEAD
Study mapping

Use this as independent command practice: read the notes, predict the output, then compare it with the example before using a real shell.

  • lfcs:operations-deployment
  • lfcs:services-logs
  • risk:read-only

Useful for

  • LPIC-1 style command-line practice
  • LFCS style performance tasks
  • Linux+ style troubleshooting review

Independent study support only. No affiliation, endorsement, exam dumps, or real exam questions.