DEVELOPER
Git Disaster Recovery & Time-Traveler
Step-by-step interactive command generator to rescue your codebase from common Git disasters: accidental hard resets, committed API keys, wrong branches, and messy merge conflicts.
Pick Your Git Emergency:
Step-by-Step Terminal Commands
Run in project root# 1. View Git's local reference ledger (history of HEAD moves)
git reflog
# 2. Find the commit hash before the reset (e.g., HEAD@{1})
# 3. Restore your branch to that exact moment:
git reset --hard HEAD@{1}
Why This Works (Under The Hood)
Git almost never deletes commit objects immediately. 'git reflog' records every single move of HEAD.
Even if you discarded commits with --hard, they are still present in your local Git database for at least 30 days.
Golden Rule:Always check 'git reflog' first before panicking. Your work is almost certainly intact.
Never Panic in Git Again
Git's object database almost never deletes your work immediately. Using git reflog and commit pointer manipulation, you can rescue virtually any destroyed state without risking project history.
Select your emergency and follow verified step-by-step commands tailored to get you back to a clean working state safely.
How to use this tool
- Select your specific Git disaster scenario from the cards above.
- Review the explanations to understand how Git handles the rescue under the hood.
- Copy individual terminal commands or click 'Copy Rescue Script'.
- Run the commands in your local project root.