text Git rebase冲突

Posted

tags:

篇首语:本文由小常识网(cha138.com)小编为大家整理,主要介绍了text Git rebase冲突相关的知识,希望对你有一定的参考价值。

When looking at Git conflict markers it can sometimes be confusing which half of the conflicting section belongs to which branch:

<<<<<<< HEAD
foo
=======
bar
>>>>>>> cb1abc6bd98cfc84317f8aa95a7662815417802d

the top half is the branch you a merging into
the bottom half is from the commit that you are trying to merge in
What this means in practice if you are doing something like git pull (which is equivalent to a git fetch followed by a git merge) is:

the top half shows your local changes
the bottom half shows the remote changes, which you are trying to merge in

GIT REBASE MASTER
==

On the other hand, if you are doing something like git rebase origin/master, you are effectively trying to merge your local changes "into" the upstream changes (by replaying them on top); that means:

the top half shows the upstream changes

the bottom half shows your local changes, which you are trying to merge in

以上是关于text Git rebase冲突的主要内容,如果未能解决你的问题,请参考以下文章

git merge和rebase的区别

git svn rebase 错过/丢失提交(在 rebase --continue 由于合并冲突)?

intellij idea git rebase冲突不显示提示框git出现游离head的解决方法

intellij idea git rebase冲突不显示提示框git出现游离head的解决方法

Git 处理分支冲突 rebase

git中merge和rebase的区别