Force-pushed away
Your agent 'cleaned up the branch' to resolve a conflict. Three days of commits are gone from GitHub.
This answers: How do I recover commits after a force push? No coding needed. 2 quick decisions.
- Supervising your AI
- Keeping data safe
Checking your access…
How do I recover commits after a force push?
Act quickly. Git rarely deletes commits immediately: the reflog on the machine that had them, or GitHub's activity history, still shows the old commit ids, and you can recreate a branch from them. Then protect your main branch against force pushes and stop agents pushing without approval.
Breaks at GitHub: Force push rewrote history
How it works
Three ways to go back
git revert 9b7d3e03a2b1c4Launchkept51f0c8aAdd order emailskept9b7d3e0Redesign checkout (broke checkout)undone by a new commite4c1a2fAdd discount codeskept
Why AI tools write this bug
Agents resolving conflicts sometimes reach for reset --hard and , which make the error go away by overwriting history.
How to fix it
- Find the lost commit id in git reflog or GitHub activity.
3 more steps, and a prompt that checks your own app for this bug. Part of Pro.
UnlockCommon questions
- What is the difference between push and force push?
- A push adds commits on top. A force push replaces the remote history with your local copy, discarding anything not in it.