Hosting Operations
Read-onlySnapshot Git Status Before Recovery
An incident starts with an unknown working tree, and you need to see whether local edits could be overwritten by recovery work.
Command
git status --short --branchBefore you run this
System impact: Read-only. Low when scoped to the shown target.
When not to use it: Do not treat status alone as a release audit; inspect the commit history and deployment pointer too.
Expected output
A short branch line for main and a modified app/config.yml entry.
System impact
Read-only. Nothing changes. Git prints the current branch and working-tree state.
Recovery / rollback: no state is changed.
When to use it
Use before reset, restore, checkout, revert, or rollback work so local edits are visible.
When not to use it
Do not treat status alone as a release audit; inspect the commit history and deployment pointer too.
next steps
Related commands
Revert the Suspect Release Commit
Undo a bad release with a new commit instead of rewriting history.
git restore -- app/config.yml && git revert --no-edit release-2026-06-25-1030
Branch a Recovered Commit
Put a name on the reflog commit before it slips away.
git branch recovered-incident-note HEAD@{1}
Restore One File From Last Good Release
Recover a config file without rolling back the whole branch.
git restore --source=release-2026-06-25-1000 -- app/config.yml
Show Files Changed Since Last Good Release
Compare the suspect release against the last known-good tag.
git diff --name-status release-2026-06-25-1000..HEAD
Find a Discarded Commit in Reflog
A reset does not mean the commit vanished.
git reflog --date=iso --format='%h %gd %gs' -6
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.
Independent study support only. No affiliation, endorsement, exam dumps, or real exam questions.