bash
git reflogNotes
Reflog is local-only and records where refs pointed over time, which makes it invaluable for recovery.
Git Reflog and Recovery Cheat Sheet
Recover commits, branches, and work after resets, rebases, deletes, and mistaken force updates.
Export
Copy the compact sheet, download it, or print it.
Download
`D` dense toggle · `C` copy all
Reflog Basics
Inspect reference movements and recent branch history changes.
bash
git log -g --oneline --decorateNotes
`git log -g` formats reflog traversal as commit log output, which many users find easier to scan.
Show reflog for a specific branch
Inspect reference updates for a named branch.
bashANYgitreflogbranch
bash
git reflog show mainNotes
Useful when the recovery target involves a branch ref rather than the current HEAD movement.
Preview reflog expiration impact
See what would be pruned from reflog without changing anything.
bashANYgitreflogmaintenance
bash
git reflog expire --expire=30.days --all --dry-runNotes
Mostly administrative, but useful when troubleshooting object reachability and retention.
Recovering Commits
Find and restore commits after destructive operations.
Restore branch to a reflog entry
Move the current branch back to a previous recorded state.
bashANYgitreflogresetrecovery
bash
git reset --hard HEAD@{3}Notes
Strong recovery option after bad rebase, reset, or merge. Verify the target first because `--hard` discards working tree changes.
Recover work into a new branch
Create a new branch from a reflog entry without moving current branch yet.
bashANYgitreflogbranchrecovery
bash
git branch recovered-work HEAD@{3}Notes
Safer than immediately hard-resetting because it preserves your current branch while giving you a recovery pointer.
Check out a lost commit directly
Inspect a recovered commit before deciding what to do with it.
bashANYgitrecoverycheckout
bash
git checkout <lost_commit_sha>Notes
Detached HEAD checkout is useful for verifying that a reflog-discovered commit is the one you want to recover.
Restore a lost commit by cherry-picking it
Apply a recovered commit onto the current branch.
bashANYgitrecoverycherry-pick
bash
git cherry-pick <lost_commit_sha>Notes
Useful when you only need one or a few recovered commits rather than rewinding the whole branch.
Find dangling commits and objects
List objects that are no longer reachable from refs.
bashANYgitfsckdanglingrecovery
bash
git fsck --lost-foundNotes
Helpful when reflog is insufficient and you suspect commits still exist as dangling objects.
Recovering Branches and HEAD States
Restore deleted branches and previous branch tips.
Create branch from ORIG_HEAD
Use ORIG_HEAD as a quick recovery anchor.
bashANYgitorig-headbranchrecovery
bash
git branch recovered-orig ORIG_HEADNotes
ORIG_HEAD often points to the pre-operation tip after merge, pull, reset, or rebase.
Search reflog for deleted branch tips
Find likely commit hashes for branch recovery.
bashANYgitreflogbranchgrep
bash
git reflog --all | grep feature-branchNotes
Search across all reflogs when recovering branch pointers that were deleted or force-updated.
Restore a branch ref manually
Move a branch ref to a specific commit hash.
bashANYgitupdate-refbranchrecovery
bash
git update-ref refs/heads/feature <commit_sha>Notes
Low-level but useful when you know the exact target and want to repair a ref directly.
Switch to a reflog entry in detached HEAD
Inspect a previous HEAD state without changing refs.
bashANYgitreflogdetached-head
bash
git switch --detach HEAD@{3}Notes
A safe way to inspect old states before deciding to branch or reset.
Safety and Maintenance
Retention, garbage collection, and recovery-friendly practices.
Set default reflog retention
Customize how long normal reflog entries are retained.
bashANYgitreflogconfiggc
bash
git config --global gc.reflogExpire 90.daysNotes
Longer reflog retention can improve recovery options in repositories with heavy history editing.
Set unreachable reflog retention
Control retention for entries that are no longer reachable.
bashANYgitreflogconfiggc
bash
git config --global gc.reflogExpireUnreachable 30.daysNotes
Important if you often rewrite history and want a wider window for recovery.
bash
git gc --prune=nowNotes
Use carefully. Immediate pruning can remove recovery options for unreachable objects sooner than expected.
Inspect loose objects and packing state
Check repository object counts and size details.
bashANYgitmaintenanceobjects
bash
git count-objects -vHNotes
Useful during repository maintenance and when reasoning about how much potentially recoverable loose object data exists.
More in Git Advanced
Git Bisect, Cherry-pick, and Submodule Cheat Sheet
Advanced workflows for regression hunting, selective commit transfer, and repository dependency management.
Git Stash, Worktree, and Clean Cheat Sheet
Temporary work preservation, multi-worktree workflows, cleanup commands, and conflict-resolution reuse.
Git Reset, Revert, and Restore Cheat Sheet
Understand the differences between reset, revert, and restore and use the right recovery command safely.
Git Rebase Cheat Sheet
Advanced rebase commands, interactive workflows, conflict handling, and branch-transplant patterns.
Git Advanced Cheat Sheet
Advanced Git commands and workflows for rewriting history, recovering commits, debugging regressions, working with multiple trees, and maintaining repositories.