git error failed to push some refs to remote

Question

For some reason  I can t push now  whereas I could do it yesterday  Maybe I messed up with configs or something   This is what happens   When I use the git push origin master    What my working directory and remote repository looks like

User · Answer

In my case there was a problem with a git pre-push hook.

Run git push --verbose to see if there are any errors.

Double check your git-hooks in the directory .git/hooks or move them temporarily to another place and see if everything works after that.

User · Answer

git error  failed to push some refs to also comes when the local repository name does match with the corresponding remote repository name  Make sure you are working on the correct pair of repository before you Pull changes to remote repository  In case you spell incorrectly and you want to remove the local repository use following steps   Remove the local repo from windows   del  F  S  Q  A  git rmdir  git Correct the local folder name  XXXX02- XXXX20  or if it is a newly created repo delete it and recreate the repo  XXXX02 Repo name changed to XXXX20   git init Remap with remote repo if it is not mapped  git remote add origin https   github com  lt username gt  XXXX20 git git push -u origin master

User · Answer

This is probably not a common problem  but it happened to me  so I ll add it as a comment here in case someone else makes the mistake I did  I created a custom pre-push file  and I forgot to end it with exit 0 That caused me to get this  quot failed to push some refs quot  error  I added exit 0 to the end of my pre-push hook and  of course  it works fine now

User · Answer

For me the Problem was  I did not add the files before the commit   git add    git commit -m  your msg

User · Answer

Remember to commit your changes before pushing to Github repo  This might fix your problem

User · Answer

In my case I misspelled the name of the branch   Locally I did something like  git push --set-upstream origin feture my-feature where my branch name was missing the a in feature   I corrected it to  git push --set-upstream origin feature my-feature And everything worked fine

User · Answer

Not commiting initial changes before pushing also causes the problem

User · Answer

Not sure if this applies  but the fix for me was to commit something locally after git init   Then I pushed to remote using --set-upstream

User · Answer

In my case closing of editor  visual studio code  solved a problem

User · Answer

This happens to me as I had a tag with the same as the branch and I tried to push the branch to remote

User · Answer

You need to give some force   Just do push --force

User · Answer

I had same problem  I was getting this problem because i had not made any commit not even initial commit and still i was trying to push   Once i did git commit -m  your msg  and then everything worked fine

User · Answer

Well if none of the above answers are working and if you have messed up something with ssh-add lately  Try  ssh-add -D

User · Answer

I was pushing existing typo  evelop  branch which I did not have checkout yet  and instead  I wanted to push a branch called  envelope   So the branch must be existing checkout out at local working copy in order to push of course  therefore that error  not to make a typo

User · Answer

I find the solution to this problem in github help   You can see it from Dealing with non-fast-forward errors  It says   You can fix this by fetching and merging the changes made on the remote branch with the changes that you have made locally       git fetch origin   Fetches updates made to an online repository   git merge origin branch   Merges updates made online with your local work   Or  you can simply use git pull to perform both commands at once     git pull origin branch   Grabs online updates and merges them with your local work

User · Answer

git push -f origin master  this one is write

User · Answer

do these  git rm --cached   git add   git commit -m upload  git push --set-upstream origin master   Happy coding

User · Answer

Best use rm -rf  git hooks and then try git push

User · Answer

I had faced same problem fixed with below steps     git init git add   git commit -m  Add your commit message  git remote add origin https   User name bitbucket org User name sample git   Above url https   User name bitbucket org User name sample git  refers to your bit bucket project url   git push -u origin master   hint  check if your git hub account link with your local git by using   git config --global user email  you example com  git config --global user name  Your Name

User · Answer

For sourcetree users  First do an initial commit or make sure you have no uncommited changes  then at the side of sourcetree there is a  REMOTES   right-click on it  and then click  Push to origin   There you go

User · Answer

git init git remote add origin https   gitlab com crew-chief-systems bot git remote -v  for checking current repository  git add -A add all files  git commit -m  Added my project  git pull --rebase origin master git push  origin master

User · Answer

Unfortunately  I could not solve the problem with the other solution but my problem was that the branch name I want to push was not accepted by remote  I change it to the correct format and accepted   it was test testing routes and needed to change it to testing route which the   is not allowed by remote    You should ensure that the branch name format is correct

User · Answer

Try this git command   git push origin master    f git push origin master --force

User · Answer

before push you have to add and commit the changes or do git push -f origin master

User · Answer

Rename your branch and then push  e g    git branch -m new-name git push -u new-name   This worked for me

User · Answer

I followed the following steps and it worked for me    rm -rf  git  git init  git add    git commit -m first message   git remote add origin  LINK   git push -u origin master

User · Answer

In my case the problem was that  strangely  there was no branch called master  I took the repository from Github

User · Answer

If you are attempting to initialize a directory with an existing GitHub repository  you should ensure you are committing changes   Try creating a file   touch initial git add initial git commit -m  initial commit  git push -u origin master   That will place a file named initial that you can delete later   Hope this answer helps  Goodluck

User · Answer

If you are using gerrit  this could be caused by an inappropriate Change-id in the commit   Try deleting the Change-Id and see what happens

User · Answer

Because maybe have nothing to push  really  no thing to push   Do like this git remote add origin https   github com donhuvy accounting133 git git remote -v git add   git commit -m quot upload quot  git push --set-upstream origin master  Change the remote repository url in your case  Command git remote -v you can skip  just for checking

User · Answer

In my case  it was my husky package that disallows the push    gt  husky - pre-push hook failed  add --no-verify to bypass   gt  husky - to debug  use  npm run prepush  error  failed to push some refs to  https   username bitbucket org username my-api git       To push it forcefully  just run git push origin master --no-verify   I ran npm run prepush to see debug the error  and this was the cause   npm ERR  code ELOCKVERIFY npm ERR  Errors were found in your npm-shrinkwrap json  run  npm install  to fix them  npm ERR      Invalid  lock file s loopback-utils 0 8 3 does not satisfy loopback-utils  0 9 0   Ran npm install and commit it  and the problem is fixed

User · Answer

Note  starting Oct  2020  any new repository is created with the default branch main  not master  And you can rename existing repository default branch from master to main  The rest of this 2014 answer has been updated to use  quot main quot   If the GitHub repo has seen new commits pushed to it  while you were working locally  I would advise using  git pull --rebase git push  The full syntax is  git pull --rebase origin main git push origin main  With Git 2 6   Sept  2015   after having done  once  git config --global pull rebase true git config --global rebase autoStash true  A simple git pull would be enough   Note  with Git 2 27 Q2 2020  a merge autostash is also available for your regular pull  without rebase  That way  you would replay  the --rebase part  your local commits on top of the newly updated origin main  or origin yourBranch  git pull origin yourBranch   See a more complete example in the chapter 6 Pull with rebase of the Git Pocket Book  I would recommend a    add and commit first git push -u origin main  That would establish a tracking relationship between your local main branch and its upstream branch  After that  any future push for that branch can be done with a simple  git push  See  quot Why do I need to explicitly push a new branch  quot    Since the OP already reset and redone its commit on top of origin main  git reset --mixed origin main git add   git commit -m  quot This is a new commit for what I originally planned to be amended quot  git push origin main  There is no need to pull --rebase  Note  git reset --mixed origin main can also be written git reset origin main  since the --mixed option is the default one when using git reset

User · Answer

In my case branch name prefix was already present at remote so basically if you have a branch name  fix  you cannot push another branch with name  fix new branch name   renaming branch solved my problem

User · Answer

It may happen when you don t have any files  Try to create a text file then follow the following commands  git add   git commit -m  first commit  git push --set-upstream origin master

User · Answer

The fact that GitHub changed master to main made me encounter this issue  So from now on  the solution to push to origin is  git push -u origin main

User · Answer

This issue comes when remote server has some extra commit which is not available in your working directory  Below is the solution to fix this issue   To get latest code from remote server to local and then push  gt git pull  gt git push   Directly do the force push to the remote server   gt git push --force  if  1 will not work then use  2 option Use below command to get all the options that is related to push  gt  git push --help

User · Answer

Github changed the default branch name from master to main  So if you created the repo recently  try pushing main branch git push origin main  This is a common mistake  beginners can make  Github Article

User · Answer

Creating a new branch solved for me   git checkout -b  lt nameOfNewBranch gt    As expected no need to merge since previous branch was fully contained in the new one

User · Answer

Did anyone try   git push -f origin master   That should solve the problem      EDIT  Based on  Mehdi    s comment below I need to clarify something about    force pushing  The git command above works safely only for the first commit  If there were already commits  pull requests or branches in previous  this resets all of it and set it from zero  If so  please refer  VonC    s detailed answer for better solution

User · Answer

If you just used git init and have added your files with git add   or something similar and have added your remote branch it might be that you just haven t committed  git commit -m  commit message   anything locally to push to the remote    I just had this error and that was my issue

User · Answer

I faced this issue but after 2 days I got a solution  Just run these two commands if you are deploying your site on GitHub pages first time  git commit -m  quot initial commit quot  git push origin  HEAD

User · Answer

git push origin  your local branch   your remote branch    If your local branch and remote branch share the same name  then can you omit your local branch name  just use git push  your remote branch   Otherwise it will throw this error

User · Answer

I created an empty repo in GitHub  and have my code locally  I faced the same issue now  as I followed the below sequence   git init git commit -m  Initial Commit  git remote add origin https   github com kavinraju Repo-Name git git add   git push -u origin master      ISSUE WAS  I tried to commit before staging the files I have    SO WE NEED TO STAGE THE FILES AND THEN COMMIT   This is the correct sequence   git init git add   git commit -m  Initial Commit  git remote add origin https   github com kavinraju Repo-Name git git push -u origin master   Since I execute the wrong sequence first  I just execute the below commands  git add   git commit -m  Initial Commit  git push -u origin master

User · Answer

Using a Git repo in Azure DevOps  the problem was a branch policy requiring that all changes to the branch must be made via pull request  Trying to push changes directly to the branch generated the error  quot failed to push some refs to     quot   I created a PR-branch and pushed without problem

[git] git error: failed to push some refs to remote

Examples related to git

Examples related to github