Updates were rejected because the remote contains work that you do

Question

I'm trying to move a local repository to bitbucket, I'm following this tutorial but when I do

git push --all bitbucket

I got the following meessage error:

To https://bitbucket.org/growtec/offshore.git
 ! [rejected]        Leonardo -> Leonardo (fetch first)
 ! [rejected]        master -> master (fetch first)
error: failed to push some refs to 'https://lrslima@bitbucket.org/growtec/offshore.git'
hint: Updates were rejected because the remote contains work that you do
hint: not have locally. This is usually caused by another repository pushing
hint: to the same ref. You may want to first integrate the remote changes
hint: (e.g., 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.

I'm on master branch and I already did a git pull but the output was the Everything up-to-date.

I saw this question but it didn't work for me

I recommend *avoiding* `git pull` entirely, but since you are using it: (1) what remotes do you have (`git remote` will list them)? (2) what is the `upstream` setting of your `master` branch name? (`git rev-parse --symbolic-full-name master@{upstream}` will show it.) (3) what is the `upstream` setting of your `Leonardo` branch name? — torek, Oct 17 '17 at 17:17

score 3 · Answer 1 · answered Oct 17 '17 at 16:36

3

You did a git pull on the master branch, but if you look closely at what your git push --all bitbucket command is doing, it's also trying to push the Leonardo branch, which you never pulled. You can try pulling this branch as well, and then push all again:

git checkout Leonardo
git pull origin Leonardo
git push --all bitbucket

answered Oct 17 '17 at 16:36

Tim Biegeleisen

502,043
27
286
360

I tried this but i'm still getting the same message error – Leonardo Lima Oct 17 '17 at 16:40
1

Did you pull `master` again, as new commits to the remote `master` may have happened since you last pulled? – Tim Biegeleisen Oct 17 '17 at 16:46
Yes, everything is up-to-date. – Leonardo Lima Oct 17 '17 at 17:25

score 3 · Answer 2 · answered Oct 17 '17 at 16:45

3

If everything is already up to date. Try git push -f origin master. -f stands for force commit. Hope this helps.

answered Oct 17 '17 at 16:45

rased

136
2
6

4

It is dangerous to force push ... It is better to solve the issue with other ways – Pascal Fares Mar 13 '19 at 14:44

score 2 · Answer 3 · answered Mar 13 '19 at 14:48

2

You need to pull (or fetch and merge) the 2 branches master and Leonardo solve all the conflicts commit then push again

answered Mar 13 '19 at 14:48

Pascal Fares

21,959
2
14
12

score 1 · Answer 4 · answered Mar 13 '19 at 13:47

1

just this code using terminal :

git push -f origin master

answered Mar 13 '19 at 13:47

Seda T.

161
1
4

1

> It is dangerous to force push ... It is better to solve the issue with other ways. – Pathros Feb 10 '20 at 01:02

score 0 · Answer 5 · answered Oct 17 '17 at 17:15

0

git pull origin master
git fetch origin Leonardo:Leonardo
git push --all bitbucket

answered Oct 17 '17 at 17:15

phd

82,685
13
120
165

7

Could you please explain how your suggestion solves the original problem. Code only answers should generally be avoided. – Nigel Ren Oct 17 '17 at 18:42

score 0 · Answer 6 · answered Aug 26 '20 at 03:58

This solved my issue Github "Updates were rejected because the remote contains work that you do not have"

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

Updates were rejected because the remote contains work that you do

6 Answers6