git merge错误：“No commit specified and merge.defaultToUpstream not set”

最新推荐文章于 2024-03-28 15:30:56 发布

a1232345

最新推荐文章于 2024-03-28 15:30:56 发布

阅读量4.8k

点赞数

分类专栏：杂项文章标签： git merge branch

本文链接：https://blog.csdn.net/a1232345/article/details/40323433

版权

杂项专栏收录该内容

14 篇文章 1 订阅

订阅专栏

问题：

$ git fetch
$ git merge

Now I get the error:

fatal: No commit specified and merge.defaultToUpstream not set.

解决办法：

Usually you do not invoke git merge without arguments (at least I don't know anyone who does). If you want that merge defaults to the tracking branch, you need to set merge.defaultToUpstream to true: git config merge.defaultToUpstream true. Your master branch has to track origin/master in this case: git branch --set-upstream master origin/master. This is done automagically if origin/master was already present when you cloned.

Personally, I do git fetch and then git merge origin/master or git pull if I have no local commits.

git merge后面需要跟参数，指明是跟的merge的哪个 branch，如git merge origin/master。