I've made a mess of my git repo and am hoping that there is a fix for this. I tried to do some upgrades of a library dependency that went bad. I couldn't find a way to undo them, so I just decided to go back to an earlier commit and then work from there, thinking that I would merge things later on. However, I wound up with origin/master being detached from the head and now I am unable to push anything to the remote repo. Here is a screen shot of the current state of things:
I couldn't care less about that branch. I just want it to go back into the hole it crawled out of. But I can't make it happen.
I've tried to revert the commit like this:
git revert 7921869
error: revert is not possible because you have unmerged files.
hint: Fix them up in the work tree, and then use 'git add/rm
hint: as appropriate to mark resolution and make a
fatal: revert failed
git push origin HEAD:master
To https://firstname.lastname@example.org/xxx/xxx.git ! [rejected] HEAD ->
error: failed to push some refs to
hint: Updates were
rejected because a pushed branch tip is behind its remote
counterpart. Check out this branch and integrate the remote
hint: (e.g. 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for
git push origin master --force
error: src refspec master does not match any.
error: failed to push
some refs to
git checkout master
git checkout e416f24
git push origin master
! [rejected] master -> master (non-fast-forward)
to push some refs to
hint: Updates were rejected because the tip of your current branch is
hint: its remote counterpart. Integrate the remote changes
hint: 'git pull ...') before pushing again.
hint: See the 'Note
about fast-forwards' in 'git push --help' for details.
git pull ...
git push origin master --force
One approach to end this madness would be to commit any work you have in this detached head state, create a new bona-fide branch, and then cherry-pick the commits you want into
master. Here is how you can do this:
git commit -m 'final commit detached HEAD' # save any remaining work git checkout -b master_detached # create new branch (perhaps optional) git checkout master # switch to master git cherry-pick <SHA-1 detached #1> # cherry-pick 1st commit git cherry-pick <SHA-1 detached #2> # cherry-pick 2nd commit ...
git cherry-pick <SHA-1> tells Git to apply a single commit whose hash is
SHA-1 to the current branch, which in this case would be
master. In other words, using cherry-pick you can effectively graft the commits you made while in the detached HEAD state onto your
master branch for safe-keeping. A cherry-pick can be thought of as a merge of one commit, and as such, you might vet merge conflicts from each cherry-pick operation.
It appears that you made a couple of bad commits on top of your
master branch in addition to the four commits you made in the detached state. In this case, you can nuke those two commits from
master. So right after the
git checkout master step above you can try the following:
git reset --hard HEAD~2
This will roll
master back from the
7921869 commit to the
e416f24 commit. After this, simple continue as above by cherry-picking the detached commits.