当我将 git commit 推送到远程存储库时，出现了以下警告：
clyde-browns-computer-2:bloccit clydiscope$ git commit -m 'Installed gem faker and generated seed data'
[seed-data fabb6ea] Installed gem faker and generated seed data
3 files changed, 26 insertions(+), 7 deletions(-)
clyde-browns-computer-2:bloccit clydiscope$ git checkout master
Switched to branch 'master'
Your branch is up-to-date with 'origin/master'.
clyde-browns-computer-2:bloccit clydiscope$ git merge seed-data
Updating 1811f8b..fabb6ea
Fast-forward
Gemfile | 1 +
Gemfile.lock | 3 +++
db/seeds.rb | 29 ++++++++++++++++++++++-------
3 files changed, 26 insertions(+), 7 deletions(-)
clyde-browns-computer-2:bloccit clydiscope$ git branch -d seed-data
Deleted branch seed-data (was fabb6ea).
clyde-browns-computer-2:bloccit clydiscope$ git push
warning: push.default is unset; its implicit value has changed in
Git 2.0 from 'matching' to 'simple'. To squelch this message
and maintain the traditional behavior, use:
\git config --global push.default matching
To squelch this message and adopt the new behavior now, use:
git config --global push.default simple
When push.default is set to 'matching', git will push local branches
to the remote branches that already exist with the same name.
Since Git 2.0, Git defaults to the more conservative 'simple'
behavior, which only pushes the current branch to the corresponding
remote branch that 'git pull' uses to update the current branch.
我切换到默认匹配只是为了解决问题，但我想知道是否有人可以详细说明这到底意味着什么，以及这种类型的事情是如何发生的。我开始使用 Git 2.0，那么这对我来说如何呢？
这意味着默认情况下，Git 仅推送当前分支，并且仅当该远程中存在同名远程分支时才推送。
这就是为什么在默认模式下，第一次推送必须是显式推送 https://stackoverflow.com/a/17096880/6309:
git push -u origin master
就你而言，master已经有一个上游分支，所以git push就足够了。
但由于未明确设置推送策略，因此警告会提醒您，默认情况下仅推送当前分支。
更多信息请访问 ”为什么推送要匹配 Git 中的默认值？ https://stackoverflow.com/a/21772695/6309"
本文内容由网友自发贡献，版权归原作者所有，本站不承担相应法律责任。如您发现有涉嫌抄袭侵权的内容，请联系:hwhale#tublm.com(使用前将#替换为@)
