How to deal with "refusing to merge unrelated histories" error

Worked for me. Thank you and God Bless! :slight_smile:

This comment should be deleted or at least not appear as first, See the accepted answer.

75 Likes

I just found that this git push problem really ruined a lot of my code. It is very very sad and frustrating. This is a huge problem for me and I wish I knew what to do to prevent it.

Its work for me. Thanks 

Managed by avoiding creating the repository with a Readme.

  1. crete without readme.md

  2. the ‘create-react-app’ command already have a ‘Readme.md’ file.

  3. Modify teh readme.md later on.

Thanks,

Arun

thanks alot… ^^

Undebatably the most useful solution ever to the most non-sensical error message ever.

thank u! work perfect

ERRRR… WRONG see accepted answer

7 Likes

THANK YOU!!

This worked for me

Thanks. You just save me.

yes,I solve mine  with this,thanks

2 Likes

To those saying this answer is wrong: It isn’t. The poster absolutely got themselves into trouble in the first place with:

$ git init
$ git add <files>
$ git commit -m "First commit from new computer"
$ git remote add origin https://github.com/roparzhhemon/myremoterepo.git

All of that should have been:

$ git clone https://github.com/roparzhhemon/myremoterepo.git

which would have automatically copied the contents of the remote repo and added it as the remote origin. You’re not meant to be doing that by hand.

If there are local files to add that aren’t in the remote repo, those can be added after the clone operation. Then the history won’t be divergent, the new commit will have the HEAD of the remote repo as its parent, and git push will go right through.

The key is right in the name of the remote: “origin”. It’s meant to be the source of your local repo’s copy of the history, not the destination for it.

The accepted answer may be the solution to this problem, when it’s already happened, but it’s much better to never get into that situation in the first place.

45 Likes

I had just created a README.md while initiating a new Repositoy. after adding remote origin the issue rised on git pull. but this is really helful to solve my problem.

This solution also works for me  :slight_smile: thanks!

1 Like

God bless you man. :slight_smile:

This worked for me too!!!

Thanks!!!

1 Like

Thank you! It works in my case.

Thanks it worked for me

Yes it worked…!! Thanks a ton :slight_smile: