I have checked out the various questions on this. The first provides a huge question and answer (relevant? not sure) and the second provides a wrong answer as best answer.
I have a branch called great-use-this
. I have another branch called master
. I want to merge great-use-this
into master, and avoid auto-merging conflicts.
What is the simplest and easiest way to do this?
Note: I have actually figured this out (using a third branch and ours
, but this would be good to have on SO anyway.
Merging is Git's way of putting a forked history back together again. The git merge command lets you take the independent lines of development created by git branch and integrate them into a single branch. Note that all of the commands presented below merge into the current branch.
When you fix your conflicted files and you are ready to merge, all you have to do is run git add and git commit to generate the merge commit. Once the commit was made , git push the changes to the branch.
Git Merge Strategies. A merge happens when combining two branches. Git will take two (or more) commit pointers and attempt to find a common base commit between them. Git has several different methods to find a base commit, these methods are called "merge strategies".
Yes, creating a third branch and doing a merge -s ours
is one solution.
But You will find the all "let's not advertised any "theirs" merging strategy" here.
Between replacing your work with one other branch work, or simply getting rid of the current work and replacing it completely by the other one, Junio C. Hamano (main Git Maintainer) prefers the second approach:
I think "
-s theirs
" is even worse. It is how you would discard what you did (perhaps because the other side has much better solution than your hack), but that can be much more easily and cleanly done with:$ git reset --hard origin/master
Some people might say "But with '
merge -s theirs
', I can keep what I did, too". That reset is simply discarding what I did.That logic also is flawed. You can instead:
$ git branch i-was-stupid $ git reset --hard origin/master
if you really want to keep record of your failure.
One big problem "
-s theirs
" has, compared to the above "reset to origin, discarding or setting aside the failed history" is that your 'master' history that your further development is based on will keep your failed crap in it forever if you did "-s theirs".Hopefully you will become a better programmer over time, and you may eventually have something worth sharing with the world near the tip of your master branch. When that happens, however, you cannot offer your master branch to be pulled by the upstream, as the wider world will not be interested in your earlier mistakes at all.
Ran into this problem the other day:
httpx://seanius.net/blog/2011/02/git-merge-s-theirs/
Update: Old url is down. Here is the article via Archive.org's Wayback Machine:
git merge -s ours ref-to-be-merged
git diff --binary ref-to-be-merged | git apply -R --index
git commit -F .git/COMMIT_EDITMSG --amend
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With