How to undo “git push –mirror”?
git push To firstname.lastname@example.org:... ! [rejected] master -> master (non-fast-forward) error: failed to push some refs to 'email@example.com:...' To prevent you from losing history, non-fast-forward updates were rejected Merge the remote changes before pushing again. See the 'Note about fast-forwards' section of 'git push --help' for details.
I tried to fix this problem and upon Googleing I came up with this line:
- How can I change the current repository I am connected to?
- cannot push to github: everything up-to-date
- Multiple git repo in one project
- Authenticate with Octokit.net and push with LibGit2Sharp to GitHub repository
- git: 'reflow' is not a git command. See 'git --help'
- Jenkins git commit for specific branch triggers build jobs for other branches too
git push --mirror
I issued the following command and now it seems that I have deleted a lot of branches from the server.
Total 0 (delta 0), reused 0 (delta 0) To firstname.lastname@example.org:... - [deleted] develop + 797beee...bafbc50 master -> master (forced update) - [deleted] milestone - [deleted] robot - [deleted] strategy * [new branch] origin/HEAD -> origin/HEAD * [new branch] origin/develop -> origin/develop * [new branch] origin/master -> origin/master * [new branch] origin/milestone -> origin/milestone * [new branch] origin/robot -> origin/robot * [new branch] origin/robot_simulator -> origin/robot_simulator * [new branch] origin/strategy -> origin/strategy * [new branch] origin/vision -> origin/vision
Can you tell me what has happened and how can I undo the change I made? (in case I deleted those branches)
2 Solutions collect form web for “How to undo “git push –mirror”?”
That implies, that the refs deleted from the server would still be in the remote locally after the push. Do not update the remotes (!).
Verify this by doing
git branch -a
on the side you pushed from (local).
It will probably show the refs that were deleted from the remote server.
[to be continued]
You could do something like:
for-each-ref refs/remotes/origin | while read sha type name do git branch "rescue_$(basename "$name")" "$sha" done
to recover the branches locally. They will be named prefixed with
rescue_ just as a precaution (in case you get funny or conflicting ref names).
origin with the name of your remote
In case you want to test the procedure in a controlled environment, here is my approach condensed to minimum steps (execute in an empty dir, e.g. /tmp/work)
git init A; (cd A; touch test; git add test; git commit -m initial; git branch test1; git branch test2; git branch test3) git clone A B (cd B; git push --mirror origin; git branch -a) cd A git for-each-ref refs/remotes/origin | while read sha type name; do git branch "rescue_$(basename "$name")" "$sha"; done git branch -a
Note how in this version, I cd into
A – which would be your github repo. You could
git clone --mirror email@example.com:... local_rescue in order to get a suitable local version of that.
I recommend you play around getting to terms with the procedure before trying it out. It never hurts to backup your repositories along the way.
You were in a situation like this:
- x - A - B - C (origin/master) \ D - E - F (master)
You wanted to do one of two things, both of which are described in the documentation that Git suggested you read:
Pull, then push, giving you this:
- x - A - B - C \ \ D - E - F - M (master, origin/master)
Force push (
git push --force), giving you this:
- x - D - E - F (master, origin/master)
git push --mirror you basically did the equivalent of force-pushing everything, making the remote repository into a mirror of your local one. This means, just like it reported, deleting everything on the remote that wasn’t in your repository.
Edit: sehe’s answer describes how to recover. If you have run
git remote update, which would have deleted the remote branches it uses to recover from, then the following could be useful. Otherwise, you’re all set.
Your best bet is to find someone else who has cloned from the remote repository (or if you’re lucky, a separate clone that you’d made), tell them not to pull/fetch/remote update, and follow sehe’s instructions from that repo.
Failing that, recovering is going to be really tricky. If you’ve interacted with any of the remote branches recently, it’s possible there will be traces in
git reflog show
Otherwise, if the deleted refs refer to commits which are ancestors of any remaining branches, you can maybe recreate them quickly. If they refer to things which aren’t ancestors of remaining branches, you can find dangling commits:
and perhaps figure out which ones had branches pointed to them.