git push rejected: error: failed to push some refs

Question

I know people have asked similar questions, but I believe the causes of their problems to be different. I did a hard reset because I had messed up my code pretty bad

 git reset --hard 41651df8fc9

I've made quite some changes, I've made some commits and now that I'm trying to push all these commits into the server I get the following error:

 ! [rejected]        master -> master (non-fast-forward)
error: failed to push some refs to '[email protected]'

Git suggests to do a git pull and that's what other people have suggested to other users. However, I believe that a git pull will merge my current code with the code that I don't want anymore (head revision). How can I do a push and forget about the version/revisions ahead of me?

Solution 1

git push -f if you have permission, but that will screw up anyone else who pulls from that repo, so be careful.

If that is denied, and you have access to the server, as canzar says below, you can allow this on the server with

git config receive.denyNonFastForwards false

Solution 2

If you are the only the person working on the project, what you can do is:

 git checkout master
 git push origin +HEAD

This will set the tip of origin/master to the same commit as master (and so delete the commits between 41651df and origin/master)

Solution 3

Just do

git pull origin [branch]

and then you should be able to push.

If you have commits on your own and didn't push it the branch yet, try

git pull --rebase origin [branch]

and then you should be able to push.

Read more about handling branches with Git.

Solution 4

'remote: error: denying non-fast-forward refs/heads/master (you should pull first)'

That message suggests that there is a hook on the server that is rejecting fast forward pushes. Yes, it is usually not recommended and is a good guard, but since you are the only person using it and you want to do the force push, contact the administrator of the repo to allow to do the non-fastforward push by temporarily removing the hook or giving you the permission in the hook to do so.

Solution 5

for me following worked, just ran these command one by one

git pull -r origin master

git push -f origin your_branch

View more solutions

Comments

[Eric]

I guess I don't have permission 'remote: error: denying non-fast-forward refs/heads/master (you should pull first)' I'm the only one working on this repo at the moment, so I'm not worried about any other branches or anything. Any ideas?

[Eric]

will this get rid of the code that I don't want anymore and keep my new code? (sorry if it's a dumb answer)

[Tim]

If you are the only person own this repo, just use git push -f, which will use your current repo replace the remote one. If there are multi users development, fast-forward is essential, otherwise, it will very easy happen distaste .

[ouah]

this will set the tip of origin/master to the same commit as master (and so delete the commits between 41651df and origin/master)

[Tim]

Update the origin repository’s master branch with the your current HEAD located branch, allowing non-fast-forward updates. So, this is the same with git push HEAD -f. For me, I think, you can use a more gentle way to do this, first, use git fetch, after that, use git rebase -i origin/master, this will let you select the commits.

[torek]

If you can log in on the remote, you can go right into the bare git repo and manually rewind the branch, with git branch -f, e.g., git branch -f rewind_the_one_I_broke 8120307 for example. You can run git log in a bare repo to find the reset-point. Note that this has the same effect as a git push -f but bypasses the hooks.

[torek]

Or, have the admin run git branch -f, which has the same effect but does not require fussing about with the pre-receive hook.

[Seanny123]

AHHHH. SHOULD HAVE READ THE COMMENTS BEFORE RUNNING THE COMMAND.

[canzar]

If you have access to the bare repository, you can temporarily update your repository configuration with git config receive.denyNonFastForwards false. I found mine was set to true by default.

[Johnny Utahh]

@canzar the git config receive.denyNonFastForwards false is required for some of my git push --force commands to work. Thanks for the reference.

[user2568374]

fatal: Couldn't find remote ref [branch]

[ASH]

this solved my issue. The main issue I had was that I changed the default branch name manually then things started falling apart. These commands solved my issue. thanks!

[cwiggo]

I had to do this to revert to a list commit e.g. git revert --hard 010d3...., then call git push origin branch -f