! [rejected] master -> master (fetch first)

Question

Is there a good way to explain how to resolve "! [rejected] master -> master (fetch first)'" in Git?

When I use this command $ git push origin master it display an error message.

! [rejected]        master -> master (fetch first)
error: failed to push some refs to 'git@github.com:zapnaa/abcappp.git'

git push origin master --force – Omar bakhsh Jan 25 '21 at 03:25 — Omar bakhsh, Jan 25 '21 at 03:25

linuxbandit · Accepted Answer · 2017-09-17T12:16:14.943

The answer is there, git is telling you to fetch first.

Probably somebody else has pushed to master already, and your commit is behind. Therefore you have to fetch, merge the changeset, and then you'll be able to push again.

If you don't (or even worse, if you force it by using the --force option), you can mess up the commit history.

EDIT: I get into more detail about the last point, since a guy here just gave the Very Bad Advice of using the --force option.

As git is a DVCS, ideally many other developers are working on the same project as you, using the same repository (or a fork of it). If you overwrite forcefully with your changeset, your repository will mismatch other people's, because "you rewrote history". You will make other people unhappy and the repository will suffer. Probably a kitten in the world will cry, too.

TL;DR

If you want to solve, fetch first (and then merge).
If you want to hack, use the --force option.

You asked for the former, though. Go for 1) always, even if you will always use git by yourself, because it is a good practice.

@cantaş `fetch` alone doesn't change your code locally because it only gets the meta-data info about the latest changes that were made from the remote repo. Basically it gives you the latest news about what happened since your last pull. If you want to bring the actual changes into your local repo you will then use `pull`. What `pull` does the same as `fetch` AND actually gets them. — minasrc, Jul 27 '22 at 07:04

score 137 · Answer 2 · answered Nov 21 '16 at 00:41

137

try:

git fetch origin master
git merge origin master

After to wrote this code I received other error: (non-fast-forward)

I write this code:

git fetch origin master:tmp
git rebase tmp
git push origin HEAD:master
git branch -D tmp

And resolved my problem

answered Nov 21 '16 at 00:41

Aurelio A

1,767
1
10
4

Same for me. That solved my problem. There are a couple of warnings. I messed up with a sub repository, but solved it with this: http://stackoverflow.com/questions/19584255/what-does-a-grey-icon-in-remote-github-mean – M. Beausoleil Jan 10 '17 at 16:17
1

@Aurelio A Your merge command is incorrect, it should be `git merge master`. – mike Jul 29 '18 at 18:21
2

Why we need to use git branch -D tmp ? – Милош Вељковић Apr 22 '19 at 21:07

score 41 · Answer 3 · answered Nov 12 '15 at 19:05

41

You should use git pull, that´s command do a git fetch and next do the git merge.

If you use a git push origin master --force command, you may have problems in the future.

answered Nov 12 '15 at 19:05

usainzg

965
9
13

1

Is it correct that you should only use --force if you're the only one on the project and you're getting frustrated trying to do your first push? – chrips Oct 20 '17 at 04:29

score 35 · Answer 4 · answered Sep 23 '16 at 20:55

35

pull is always the right approach but one exception could be when you are trying to convert a none-Git file system to a Github repository. There you would have to force the first commit in.

git init
git add README.md
git add .
git commit -m "first commit"
git remote add origin https://github.com/userName/repoName.git
git push --force origin master

answered Sep 23 '16 at 20:55

J D

707
7
13

1

works for me, I started again a new project (same repo) and I wanted to replace it. – ucotta Jun 02 '17 at 18:46

score 27 · Answer 5 · edited Jan 17 '20 at 15:57

27

As it is stated in the Error message you have to "fetch first." This worked for me. Use the command:

git fetch origin master

Then follow these steps to merge:

git pull origin master
git add .
git commit -m 'your commit message'
git push origin master

edited Jan 17 '20 at 15:57

Adrian Mole

49,934
160
51
83

answered Jan 17 '20 at 15:35

Amila Weerasinghe

791
7
10

score 25 · Answer 6 · answered Feb 10 '15 at 12:15

25

Try this git command

git push origin master --force

or short of force -f

git push origin master -f

answered Feb 10 '15 at 12:15

3

This overrides git push restriction. Not recommended for teamwork. From git push documentation: _If somebody else built on top of your original history while you are rebasing, the tip of the branch at the remote may advance with her commit, and blindly pushing with --force will_ **lose her work**. – Casey Oct 04 '17 at 09:57

score 9 · Answer 7 · edited May 12 '20 at 20:49

9

Follow the steps given below as I also had the same problem:

$ git pull origin master --allow-unrelated-histories

(To see if local branch can be easily merged with remote one)

$ git push -u origin master

(Now push entire content of local git repository to your online repository)

edited May 12 '20 at 20:49

dippas

58,591
15
114
126

answered May 12 '20 at 17:33

Bhavdeep Kaur

89
1
2

score 5 · Answer 8 · answered Dec 08 '21 at 07:42

5

This happens when your teammate have already committed. so his commit is on top. To avoid you do rebase (merge , fetch).

I solved my issue with the following.

git pull --rebase origin master
git push -u origin master

you can see logs git log.

answered Dec 08 '21 at 07:42

majid asad

303
5
14

score 4 · Answer 9 · answered Oct 29 '17 at 12:11

You can use the following command: First clone a fresh copy of your repo, using the --mirror flag:

$ git clone --mirror git://example.com/some-big-repo.git

Then follow the codes accordingly:

Adding an existing project to GitHub using the command line

Even if that doesn't work, you can simply code:

$ git push origin master --force

or

$ git push origin master -f

score 4 · Answer 10 · edited Jan 13 '21 at 08:32

4

Quickest solution-

DO a git log-> You will see someone probably has pushed some code post the time you had pulled the latest codebase.
DO a git pull --rebase, this will first, rewind head to replay your work on top of it and then apply your committed changes to the same.
You are now all set for a git push.

edited Jan 13 '21 at 08:32

Dharman

30,962
25
85
135

answered Jan 13 '21 at 08:26

Raju Kumar

41
1

score 3 · Answer 11 · edited Aug 25 '19 at 15:44

3

This worked for me:

$ git add .
$ git commit -m "commit"
$ git push origin master --force

edited Aug 25 '19 at 15:44

Pingolin

3,161
6
25
40

answered Aug 25 '19 at 14:16

Yamuna Bangaru

49
2

score 3 · Answer 12 · answered Feb 03 '22 at 18:22

3

! [rejected] master -> master (fetch first)

in this error showing time if you first checking your folder place correct path. And type: -

git push origin master --force

answered Feb 03 '22 at 18:22

Dilshad Shibin

78
6

1

As it’s currently written, your answer is unclear. Please [edit] to add additional details that will help others understand how this addresses the question asked. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community Feb 04 '22 at 00:15

score 2 · Answer 13 · answered Feb 05 '17 at 20:42

It's likely that someone else (e.g. your colleague) has put commits onto origin/master that aren't in your local master branch, and you are trying to push some commits from your local branch to the server. In 99% of cases, assuming you don't want to erase their work from origin, you have two options:

2) Merge their changes into your local branch, and then push the merged result. git checkout master git pull # resolve conflicts here git push

(Note that git pull is essentially just a git fetch and a git merge in this case.)

1) Rebase your local branch, so that it looks like your colleague made their commits first, and then you made your commits. This keeps the commit history nice and linear - and avoids a "merge commit". However, if you have conflicts with your colleague's changes, you may have to resolve those conflicts for each of your commits (rather than just once) in the worst case. Essentially this is nicer for everyone else but more effort for you. git pull --rebase # resolve conflicts here git push

(Note that git pull --rebase is essentially a git fetch and a git rebase origin/master.)

score 2 · Answer 14 · answered Oct 04 '17 at 14:11

2

Sometimes it happens when you duplicate files typically README sort of.

answered Oct 04 '17 at 14:11

Jarosław Cichoń

542
1
4
8

score 2 · Answer 15 · edited Mar 21 '19 at 08:41

2

Your error might be because of the merge branch.
Just follow this:

step 1 : git pull origin master (in case if you get any message then ignore it)
step 2 : git add .
step 3 : git commit -m 'your commit message'
step 4 : git push origin master

edited Mar 21 '19 at 08:41

סטנלי גרונן

2,917
23
46
68

answered Mar 21 '19 at 07:30

divyang hirpara

31
3

score 2 · Answer 16 · answered Oct 02 '21 at 17:56

2

I had faced this error while pressing the git push command.

The problem solved by simply adding -force after git push
Solution: git push -fource

answered Oct 02 '21 at 17:56

Mahabub Azam

51
4

score 2 · Answer 17 · answered Nov 19 '21 at 16:43

When we try to push the folder on Github using below-mentioned command

  $ git push origin master

and get the error like this:

To https://github.com/Raushan1156/QR-Code.git
 ! [rejected]        master -> master (fetch first)
error: failed to push some refs to 'https://github.com/Raushan1156/QR-Code.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.

Try this command to solve your issue, it's solved my error.

$ git push origin master --force

One Pic has been attached for a visual explanation.

score 2 · Answer 18 · answered Oct 21 '22 at 09:55

! [rejected] main -> main (fetch first) error: failed to push some refs to 'https://github.com/Wasif-M/Micard-Flutter.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.

Use this command after that:

git push -f origin main

i hope error will remove and your repository will commit to gitHub

user3826395 · Answer 19 · 2020-06-19T10:23:41.420

1

I overcame this by checking-out a new branch like this :

# git checkout -b newbranch <SHA of master>

# git branch
* newbranch
  master

# git push -u <repo_url_alias> newbranch

You are left with 2 branch : Master and newbranch , that you can manage to merge later.

edited Jun 19 '20 at 10:23

answered Jun 19 '20 at 07:49

user3826395

13
3

score 1 · Answer 20 · answered Feb 03 '22 at 19:58

1

It is happen when you create a repository in GitHub and select README or .gitignore or license files. delete repasotory if it is empty and create it again without selecting README ,.gitignore or license files.

answered Feb 03 '22 at 19:58

Darwin

1,695
1
19
29

score 1 · Answer 21 · answered Mar 22 '23 at 00:49

1

to Solve it added a "--force"

git push --force origin master

or pull it first and pull

answered Mar 22 '23 at 00:49

Ahmed Ramadan

181
1
4

score 0 · Answer 22 · answered Jul 08 '20 at 12:19

0

You just have to mention your branch name along with your remote name.

git fetch origin
git merge origin/master

answered Jul 08 '20 at 12:19

Amit Kharel

104
4

Arijit Kundu · Answer 23 · 2020-07-23T23:18:35.433

0

The reason it happened in my case was when creating the GitHub rep link, I initialized it with README file

While creating Git remote do not initialize it with README file otherwise it would show err

Don't do that & it will definitely work fine Instead initialize it with the readme file if you wish to after pushing to the master branch

edited Jul 23 '20 at 23:18

answered Jul 23 '20 at 12:12

Arijit Kundu

478
4
16

score 0 · Answer 24 · edited Aug 25 '20 at 04:26

This worked for me, since none of the other solutions worked for me. NOT EVEN FORCE!

https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line

Just had to go through Git Bash

cd REPOSITORY-NAME
git add .
git commit -m "Resolved merge conflict by incorporating both suggestions."

Then back to my cmd and I could: git push heroku master which in my case was the problem.

score 0 · Answer 25 · answered Jun 14 '22 at 23:41

0

It is very easy to fix, run the following command:

git fetch origin master

answered Jun 14 '22 at 23:41

Diana

1,091
1
9
11

score 0 · Answer 26 · answered Mar 11 '23 at 21:27

If this is your first commit and you are trying to push local code to a new repository, you probably are getting this error because you added a README when you created the repo on github. Next time you create a new repo, do it WITHOUT adding a README on github.

! [rejected] master -> master (fetch first)

26 Answers26

Linked

Related