Github Updates were rejected because the remote contains work that you do not have locally

Question

I created a new repo  cloned it  added files to the directory  added them with add -A  committed changes  and when I try to push using git push  lt repo name gt  master I get   hint  Updates were rejected because the remote contains work that you do not have locally  This is usually caused by another repository pushing to the same ref  You may want to first merge the remote changes  e g   hint   git pull   before pushing again   This doesn t seem to make sense since it s a new repo and contains only a readme file

User · Answer

The issue is because the local is not up-to-date with the master branch that is why we are supposed to pull the code before pushing it to the git git add   git commit -m  Comments to be added  git pull origin master git push origin master

User · Answer

I followed these steps   Pull the master   git pull origin master   This will sync your local repo with the Github repo  Add your new file and then   git add     Commit the changes   git commit -m  adding new file  Xyz    Finally  push the origin master   git push origin master   Refresh your Github repo  you will see the newly added files

User · Answer

If you are using Visual S2019  Create a new local branch as shown in following  and then push the changes to the repo

User · Answer

The error possibly comes because of the different structure of the code that you are committing and that present on GitHub  It creates conflicts which can be solved by   git pull   Merge conflicts resolving   git push   If you confirm that your new code is all fine you can use   git push -f origin master   Where -f stands for  force commit

User · Answer

The supplied answers didn t work for me    I had an empty repo on GitHub with only the LICENSE file and a single commit locally  What worked was     git fetch   git merge --allow-unrelated-histories Merge made by the  recursive  strategy   LICENSE   21                        1 file changed  21 insertions     create mode 100644 LICENSE   Also before merge you may want to     git branch --set-upstream-to origin master Branch  master  set up to track remote branch  master  from  origin

User · Answer

You may refer to  How to deal with  quot refusing to merge unrelated histories quot  error    git pull --allow-unrelated-histories   git push -f origin master

User · Answer

This happens if you initialized a new github repo with README and or LICENSE file  git remote add origin    your github url     pull those changes  git pull origin master      or optionally   git pull origin master --allow-unrelated-histories  if you have initialized repo in github and also committed locally    now  push your work to your new repo  git push origin master   Now you will be able to push your repository to github  Basically  you have to merge those new initialized files with your work  git pull fetches and merges for you  You can also fetch and merge if that suits you

User · Answer

If this is your first push  just change the   git push  lt repo name gt  master   change it like this   git push -f  lt repo name gt  master

[github] Github "Updates were rejected because the remote contains work that you do not have locally."

Examples related to github