blocks|key|2967621|text|git+push可以根据此配置推送所有分支或单个分支：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2967622|推送所有分支|BOLD|2967623|git+config+--global+push.default+matching|code-block|syntax|javascript|2967624|它会将所有分支推送到远程分支，并合并它们。如果您不想推送所有分支，如果您完全指定了当前分支的名称，则可以推送当前分支，但这与default没有太大区别。|2967625|如果命名的上游分支与相同，则仅推送当前分支|2967626|git+config+--global+push.default+simple|2967627|因此，在我看来，使用此选项并逐个分支推送您的代码更好。最好是手动或单独推送分支。|2967628|entityMap^0|0|8|0|0|6|0|0|1Q|7|0|E|7|0|0|0|14|0^^$0|@$1|2|3|4|5|6|7|X|8|@$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|10|8|@$9|11|A|12|B|H]]|D|@]|E|$]]|$1|I|3|J|5|K|7|13|8|@]|D|@]|E|$L|M]]|$1|N|3|O|5|6|7|14|8|@$9|15|A|16|B|C]]|D|@]|E|$]]|$1|P|3|Q|5|6|7|17|8|@$9|18|A|19|B|H]]|D|@]|E|$]]|$1|R|3|S|5|K|7|1A|8|@]|D|@]|E|$L|M]]|$1|T|3|U|5|6|7|1B|8|@$9|1C|A|1D|B|H]]|D|@]|E|$]]|$1|V|3|-4|5|6|7|1E|8|@]|D|@]|E|$]]]|W|$]]

<code>git push</code> can push all branches or a single one dependent on this configuration:
Push all branches
<pre><code>git config --global push.default matching
</code></pre>
It will push all the branches to the remote branch and would merge them.
If you don't want to push all branches, you can push the current branch if you fully specify its name, but this is much is not different from <code>default</code>.
Push only the current branch if its named upstream is identical
<pre><code>git config --global push.default simple
</code></pre>
So, it's better, in my opinion, to use this option and push your code branch by branch. It's better to push branches manually and individually.

blocks|key|2755064|text|来自GIT文档：Git+Docs|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2755065|下面提供了完整的信息。简而言之，仅当current+working+branch在遥控器上具有相同的名称时，simple才会推送它。对于初学者来说，这是一个非常好的设置，并且将成为GIT+2.0中的默认设置|style|CODE|2755066|而matching将在本地推送远程上具有相同名称的所有分支。(不考虑您当前的工作分支)。这意味着可能会推送许多不同的分支，包括那些您可能甚至不想共享的分支。|2755067|在我个人的使用中，我通常使用一个不同的选项：current，它推送当前的工作分支(因为我总是分支任何更改)。但对于初学者，我建议使用simple|2755068|2755069|+push.default|blockquote|2755070|2755071|定义如果没有显式给出refspec，git推送应该采取的操作。不同的值非常适合特定的工作流；例如，在纯粹的中央工作流中(即抓取源等于推送目的地)，上游可能是您想要的。可能的值包括：|2755072|nothing+-除非显式给出refspec，否则不要推送任何内容(错误)。这主要是为那些希望通过始终明确的方式来避免错误的人而设计的。|2755073|当前-推送当前分支以更新接收端上具有相同名称的分支。可在中心工作流和非中心工作流中工作。|2755074|upstream+-将当前分支推回到更改通常集成到当前分支中的分支(称为@{upstream})。只有当您推送到通常从中提取的相同存储库(即中央工作流)时，此模式才有意义。|2755075|简单-在集中式工作流中，如果上游分支的名称与本地分支名称不同，则会像上游一样工作，并增加安全性，以拒绝推送。|2755076|当推送到与您通常使用的遥控器不同的遥控器时，请按当前状态工作。这是最安全的选择，适合初学者。|2755077|此模式将成为Git2.0的默认模式。|2755078|匹配-推送两端具有相同名称的所有分支。这使得您正在推送的存储库记住将被推出的分支集(例如，如果您总是在那里推送maint和master，而没有其他分支，那么您推送到的存储库将具有这两个分支，并且您的本地maint和master将被推送到那里)。|2755079|要有效地使用此模式，您必须确保在运行git+push之前，您将推出的所有分支都已准备好推出，因为此模式的主要目的是允许您一次性推出所有分支。如果您通常只在一个分支上完成工作并推送结果，而其他分支尚未完成，则此模式不适合您。此外，这种模式不适合推送到共享的中央存储库，因为其他人可能会在那里添加新的分支，或者更新您控制之外的现有分支的提示。|2755080|这是目前的默认设置，但是Git2.0会将默认设置更改为simple。|2755081|entityMap|0|LINK|mutability|MUTABLE|url|http://git-scm.com/docs/git-config^0|8|8|0|0|I|M|1I|6|2I|7|0|1|8|0|M|7|1U|6|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1I|8|@]|9|@$A|1J|B|1K|1|1L]]|C|$]]|$1|D|3|E|5|6|7|1M|8|@$A|1N|B|1O|F|G]|$A|1P|B|1Q|F|G]|$A|1R|B|1S|F|G]]|9|@]|C|$]]|$1|H|3|I|5|6|7|1T|8|@$A|1U|B|1V|F|G]]|9|@]|C|$]]|$1|J|3|K|5|6|7|1W|8|@$A|1X|B|1Y|F|G]|$A|1Z|B|20|F|G]]|9|@]|C|$]]|$1|L|3|-4|5|6|7|21|8|@]|9|@]|C|$]]|$1|M|3|N|5|O|7|22|8|@]|9|@]|C|$]]|$1|P|3|-4|5|6|7|23|8|@]|9|@]|C|$]]|$1|Q|3|R|5|6|7|24|8|@]|9|@]|C|$]]|$1|S|3|T|5|6|7|25|8|@]|9|@]|C|$]]|$1|U|3|V|5|6|7|26|8|@]|9|@]|C|$]]|$1|W|3|X|5|6|7|27|8|@]|9|@]|C|$]]|$1|Y|3|Z|5|6|7|28|8|@]|9|@]|C|$]]|$1|10|3|11|5|6|7|29|8|@]|9|@]|C|$]]|$1|12|3|13|5|6|7|2A|8|@]|9|@]|C|$]]|$1|14|3|15|5|6|7|2B|8|@]|9|@]|C|$]]|$1|16|3|17|5|6|7|2C|8|@]|9|@]|C|$]]|$1|18|3|19|5|6|7|2D|8|@]|9|@]|C|$]]|$1|1A|3|-4|5|6|7|2E|8|@]|9|@]|C|$]]]|1B|$1C|$5|1D|1E|1F|C|$1G|1H]]]]

From GIT documentation: <a href="http://git-scm.com/docs/git-config" rel="noreferrer">Git Docs</a>

Below gives the full information. In short, <code>simple</code> will only push the <code>current working branch</code> and even then only if it also has the same name on the remote. This is a very good setting for beginners and will become the default in <code>GIT 2.0</code>

Whereas <code>matching</code> will push all branches locally that have the same name on the remote. (Without regard to your current working branch ). This means potentially many different branches will be pushed, including those that you might not even want to share.

In my personal usage, I generally use a different option: <code>current</code> which pushes the current working branch, (because I always branch for any changes). But for a beginner I'd suggest <code>simple</code>

<blockquote>
 push.default 
 Defines the action git push should take if no refspec is
 explicitly given. Different values are well-suited for specific
 workflows; for instance, in a purely central workflow (i.e. the fetch
 source is equal to the push destination), upstream is probably what
 you want. Possible values are:
 
 nothing - do not push anything (error out) unless a refspec is
 explicitly given. This is primarily meant for people who want to avoid
 mistakes by always being explicit.
 
 current - push the current branch to update a branch with the same
 name on the receiving end. Works in both central and non-central
 workflows.
 
 upstream - push the current branch back to the branch whose changes
 are usually integrated into the current branch (which is called
 @{upstream}). This mode only makes sense if you are pushing to the
 same repository you would normally pull from (i.e. central workflow).
 
 simple - in centralized workflow, work like upstream with an added
 safety to refuse to push if the upstream branch's name is different
 from the local one.
 
 When pushing to a remote that is different from the remote you
 normally pull from, work as current. This is the safest option and is
 suited for beginners.
 
 This mode will become the default in Git 2.0.
 
 matching - push all branches having the same name on both ends. This
 makes the repository you are pushing to remember the set of branches
 that will be pushed out (e.g. if you always push maint and master
 there and no other branches, the repository you push to will have
 these two branches, and your local maint and master will be pushed
 there).
 
 To use this mode effectively, you have to make sure all the branches
 you would push out are ready to be pushed out before running git push,
 as the whole point of this mode is to allow you to push all of the
 branches in one go. If you usually finish work on only one branch and
 push out the result, while other branches are unfinished, this mode is
 not for you. Also this mode is not suitable for pushing into a shared
 central repository, as other people may add new branches there, or
 update the tip of existing branches outside your control.
 
 This is currently the default, but Git 2.0 will change the default to
 simple.
</blockquote>

blocks|key|164278|text|Git+v2.0发行说明|type|unstyled|depth|inlineStyleRanges|entityRanges|data|164279|向后兼容性说明|164280|当git+push+[$there]没有说明要推送什么时，到目前为止，我们使用的是传统的“匹配”语义(只要那里已经有同名的分支，所有的分支都会被发送到远程)。在Git2.0中，默认的是“简单”语义，它推送：|offset|length|style|CODE|164281|仅将当前分支|164282|到具有相同名称的分支，并且仅当将当前分支设置为与该远程分支集成时(如果您正在推送到与从中提取相同的远程分支)；或者|unordered-list-item|164283|164284|到具有相同名称的分支(如果您正在推送到不是通常从中提取的远程分支)。|164285|164286|您可以使用配置变量"push.default“来更改此设置。例如，如果你是一个想要继续使用“匹配”语义的老手，你可以将变量设置为“匹配”。请阅读文档以了解其他可能性。|164287|如果在子目录内运行git+add+-u和git+add+-A，但没有指定要在命令行中添加哪些路径，则它们将对整个树进行操作，以与git+commit+-a和其他命令保持一致(这些命令仅用于对当前子目录进行操作)。如果您希望将操作限制在当前目录，则可以使用git+add+-u+.或git+add+-A+.。|164288|git+add+<path>现在与git+add+-A+<path>相同，因此git+add+dir/将注意到您从目录中删除的路径并记录删除。在旧版本的Git中，git+add+<path>习惯于忽略删除。如果你真的想要，你可以说git+add+--ignore-removal+<path>在<path>中只添加添加或修改过的路径。|164289|entityMap^0|0|0|1|H|0|0|0|0|0|0|0|9|A|K|A|1S|D|3J|C|3W|C|0|0|E|H|H|13|C|29|E|37|V|43|6|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|12|8|@$F|13|G|14|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|15|8|@]|9|@]|A|$]]|$1|L|3|M|5|N|7|16|8|@]|9|@]|A|$]]|$1|O|3|K|5|N|7|17|8|@]|9|@]|A|$]]|$1|P|3|Q|5|N|7|18|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|19|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1A|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1B|8|@$F|1C|G|1D|H|I]|$F|1E|G|1F|H|I]|$F|1G|G|1H|H|I]|$F|1I|G|1J|H|I]|$F|1K|G|1L|H|I]]|9|@]|A|$]]|$1|W|3|X|5|6|7|1M|8|@$F|1N|G|1O|H|I]|$F|1P|G|1Q|H|I]|$F|1R|G|1S|H|I]|$F|1T|G|1U|H|I]|$F|1V|G|1W|H|I]|$F|1X|G|1Y|H|I]]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1Z|8|@]|9|@]|A|$]]]|Z|$]]

<h1>Git v2.0 Release Notes</h1>

<h2>Backward compatibility notes</h2>

When <code>git push [$there]</code> does not say what to push, we have used the
traditional "matching" semantics so far (all your branches were sent
to the remote as long as there already are branches of the same name
over there). In Git 2.0, the default is now the "simple" semantics,
which pushes:

<ul>
<li>only the current branch to the branch with the same name, and only
when the current branch is set to integrate with that remote
branch, if you are pushing to the same remote as you fetch from; or</li>
<li>only the current branch to the branch with the same name, if you
are pushing to a remote that is not where you usually fetch from.</li>
</ul>

You can use the configuration variable "push.default" to change
this. If you are an old-timer who wants to keep using the
"matching" semantics, you can set the variable to "matching", for
example. Read the documentation for other possibilities.

When <code>git add -u</code> and <code>git add -A</code> are run inside a subdirectory
without specifying which paths to add on the command line, they
operate on the entire tree for consistency with <code>git commit -a</code> and
other commands (these commands used to operate only on the current
subdirectory). Say <code>git add -u .</code> or <code>git add -A .</code> if you want to
limit the operation to the current directory.

<code>git add &lt;path&gt;</code> is the same as <code>git add -A &lt;path&gt;</code> now, so that
<code>git add dir/</code> will notice paths you removed from the directory and
record the removal. In older versions of Git, <code>git add &lt;path&gt;</code> used
to ignore removals. You can say <code>git add --ignore-removal &lt;path&gt;</code> to
add only added or modified paths in <code>&lt;path&gt;</code>, if you really want to.

I have been using git for a while now, but I have never had to set up a new remote repo myself and I have been curious on doing so. I have been reading tutorials and I am confused on how to get "git push" to work. 

If I simply use <code>git push</code> it asks me to see up a default branch(?) to point to? What is the difference between these two options it supplies me with?

<pre><code>git config --global push.default matching
git config --global push.default simple
</code></pre>

Matching just pushes whatever branches I have on my local repo, and if they don't match I have to then manually tell it to push whatever new local branches I have, correct? Is this best practice to use or is simple best?

Git - What is the difference between push.default "matching" and "simple"

我使用git已经有一段时间了，但我自己从来没有设置过一个新的远程repo，我对此一直很好奇。我一直在阅读教程，我对如何让"git push“工作感到困惑。如果我简单地使用git push，它会要求我看到一个默认的分支(？)指向什么？它为我提供的这两个选项之间有什么区别？git config --global push....

问push.default“匹配”和“简单”的区别是什么？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问push.default“匹配”和“简单”的区别是什么？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问push.default“匹配”和“简单”的区别是什么？
EN