blocks|key|81258|text|推送新分支时的git+push输出|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|81259|>+git+checkout+-b+new_branch
Switched+to+a+new+branch+'new_branch'
>+git+push
fatal:+The+current+branch+new_branch+has+no+upstream+branch.
To+push+the+current+branch+and+set+the+remote+as+upstream,+use

++++git+push+--set-upstream+origin+new_branch|code-block|syntax|javascript|81260|一个简单的git+push假设当前本地分支正在跟踪的远程分支已经存在。如果不存在这样的远程分支，并且您想要创建它，则必须使用-u+(--set-upstream的缩写形式)标志指定它。|81261|为什么会这样呢？我猜实现者觉得在遥控器上创建分支是一个非常重要的操作，应该很难出错。git+push是你一直在做的事情。|81262|“默认情况下，分支不是要推送的新更改吗？”我要说的是，Git中的“一个变化”就是一个提交。分支是指向提交的指针。对我来说，更有意义的是将推送看作是将提交推到其他存储库的东西。推送哪些提交取决于您所在的分支以及该分支与远程分支的跟踪关系。|81263|您可以在Remote+Branches+chapter+of+the+Pro+Git+book中阅读有关跟踪分支的更多信息。|81264|entityMap|0|LINK|mutability|MUTABLE|url|http://git-scm.com/book/en/Git-Branching-Remote-Branches^0|7|8|0|0|5|8|1Q|2|1U|E|0|16|8|0|0|4|17|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@$9|11|A|12|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|13|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|14|8|@$9|15|A|16|B|C]|$9|17|A|18|B|C]|$9|19|A|1A|B|C]]|D|@]|E|$]]|$1|M|3|N|5|6|7|1B|8|@$9|1C|A|1D|B|C]]|D|@]|E|$]]|$1|O|3|P|5|6|7|1E|8|@]|D|@]|E|$]]|$1|Q|3|R|5|6|7|1F|8|@]|D|@$9|1G|A|1H|1|1I]]|E|$]]|$1|S|3|-4|5|6|7|1J|8|@]|D|@]|E|$]]]|T|$U|$5|V|W|X|E|$Y|Z]]]]

Output of <code>git push</code> when pushing a new branch

<pre><code>&gt; git checkout -b new_branch
Switched to a new branch 'new_branch'
&gt; git push
fatal: The current branch new_branch has no upstream branch.
To push the current branch and set the remote as upstream, use

 git push --set-upstream origin new_branch
</code></pre>

A simple <code>git push</code> assumes that there already exists a remote branch that the current local branch is tracking. If no such remote branch exists, and you want to create it, you must specify that using the <code>-u</code> (short form of <code>--set-upstream</code>) flag.

Why this is so? I guess the implementers felt that creating a branch on the remote is such a major action that it should be hard to do it by mistake. <code>git push</code> is something you do all the time.

"Isn't a branch a new change to be pushed by default?" I would say that "a change" in Git is a commit. A branch is a pointer to a commit. To me it makes more sense to think of a push as something that pushes commits over to the other repositories. Which commits are pushed is determined by what branch you are on and the tracking relationship of that branch to branches on the remote.

You can read more about tracking branches in the <a href="http://git-scm.com/book/en/Git-Branching-Remote-Branches">Remote Branches chapter of the Pro Git book</a>.

blocks|key|298504|text|我不能这么快就找到原始开发人员的理由，但我可以根据几年的Git经验给你一个有根据的猜测。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|298505|不，并不是每个分支都是你想要推向外界的东西。这可能代表了一项私人实验。|298506|此外，git+push应该将所有分支发送到哪里？Git可以使用多个远程服务器，您可能希望在每个远程服务器上使用不同的分支集。例如，中央项目Git可以具有发布分支；Git可以具有用于审查的主题分支；并且本地GitHub服务器可以具有包含本地配置的分支。如果git+push将所有分支都推送到当前分支跟踪的遥控器，这种方案很容易搞砸。|offset|length|style|CODE|298507|entityMap^0|0|0|3|8|3J|8|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@$F|O|G|P|H|I]|$F|Q|G|R|H|I]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|K|$]]

I couldn't find a rationale by the original developers this quickly, but I can give you an educated guess based on a few years of Git experience.

No, not every branch is something you want to push to the outside world. It might represent a private experiment.

Moreover, where should <code>git push</code> send all the branches? Git can work with multiple remotes and you may want to have different sets of branches on each. E.g. a central project GitHub repo may have release branches; a GitHub fork may have topic branches for review; and a local Git server may have branches containing local configuration. If <code>git push</code> would push all branches to the remote that the current branch tracks, this kind of scheme would be easy to screw up.

blocks|key|81327|text|第一次检查|type|unstyled|depth|inlineStyleRanges|entityRanges|data|81328|第1步：git+remote+-v|offset|length|style|CODE|81329|//如果找到git初始化，则删除或跳过步骤2|81330|第-2步：git+remote+rm+origin|81331|//然后全局配置您的邮箱地址git|81332|第-3步：git+config+--global+user.email+"youremail@example.com"|81333|第-4步：git+initial|81334|第5步：git+commit+-m+"Initial+Project"|81335|//如果已经添加项目存储库，则跳过步骤6|81336|第6步：git+remote+add+origin+%25repo+link+from+bitbucket.org%25|81337|第7步：git+push+-u+origin+master|81338|entityMap^0|0|4|D|0|0|5|K|0|0|5|1I|0|5|B|0|4|V|0|0|4|1G|0|4|P|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|12|8|@$D|13|E|14|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|15|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|16|8|@$D|17|E|18|F|G]]|9|@]|A|$]]|$1|L|3|M|5|6|7|19|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|1A|8|@$D|1B|E|1C|F|G]]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1D|8|@$D|1E|E|1F|F|G]]|9|@]|A|$]]|$1|R|3|S|5|6|7|1G|8|@$D|1H|E|1I|F|G]]|9|@]|A|$]]|$1|T|3|U|5|6|7|1J|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|1K|8|@$D|1L|E|1M|F|G]]|9|@]|A|$]]|$1|X|3|Y|5|6|7|1N|8|@$D|1O|E|1P|F|G]]|9|@]|A|$]]|$1|Z|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]]|10|$]]

At first check 

Step-1: <code>git remote -v</code> 
//if found git initialize then remove or skip step-2

Step-2: <code>git remote rm origin</code> 
//Then configure your email address globally git

Step-3: <code>git config --global user.email "youremail@example.com"</code>

Step-4: <code>git initial</code>

Step-5: <code>git commit -m "Initial Project"</code> 
//If already add project repo then skip step-6

Step-6: <code>git remote add origin %repo link from bitbucket.org%</code> 

Step-7: <code>git push -u origin master</code>

blocks|key|298598|text|如果您启用了首次从新分支推送新更改。并获得以下错误：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|298599|*git+push+-f
fatal:+The+current+branch+Coding_Preparation+has+no+upstream+branch.|code-block|syntax|javascript|298600|要推送当前分支并将遥控器设置为上游，请使用|298601|git+push+-u+origin+new_branch_name


**+Successful+Result:**+
+git+push+-u+origin+Coding_Preparation
Enumerating+objects:+5,+done.
Counting+objects:+100%25+(5/5),+done.
Delta+compression+using+up+to+4+threads
Compressing+objects:+100%25+(3/3),+done.
Writing+objects:+100%25+(3/3),+599+bytes+%7C+599.00+KiB/s,+done.
Total+3+(delta+0),+reused+0+(delta+0)
remote:
remote:+Create+a+pull+request+for+'Coding_Preparation'+on+GitHub+by+visiting:+...
+*+[new+branch]++++++Coding_Preparation+->+Coding_Preparation
Branch+'Coding_Preparation'+set+up+to+track+remote+branch+'Coding_Preparation'+from+'origin'.|298602|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

If you enable to push new changes from your new branch first time.
And getting below error:

<pre><code>*git push -f
fatal: The current branch Coding_Preparation has no upstream branch.
</code></pre>

To push the current branch and set the remote as upstream, use

<pre><code>git push -u origin new_branch_name


** Successful Result:** 
 git push -u origin Coding_Preparation
Enumerating objects: 5, done.
Counting objects: 100% (5/5), done.
Delta compression using up to 4 threads
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 599 bytes | 599.00 KiB/s, done.
Total 3 (delta 0), reused 0 (delta 0)
remote:
remote: Create a pull request for 'Coding_Preparation' on GitHub by visiting: ...
 * [new branch] Coding_Preparation -&gt; Coding_Preparation
Branch 'Coding_Preparation' set up to track remote branch 'Coding_Preparation' from 'origin'.
</code></pre>

I am new in <code>git</code> and I am practicing. I created a local branch but I saw that when I did <code>git push</code> my branch was not uploaded to the repository. I had to actually do: <code>git push -u origin --all</code>. 
Why is this? Isn't a branch a new change to be pushed by default? Why do I need to run the second command?

Why do I need to explicitly push a new branch?

服务器

GitHub

我是git的新手，我正在练习。我创建了一个本地分支，但是我发现当我使用git push时，我的分支并没有上传到存储库。我必须要做的是：git push -u origin --all。为什么会这样呢？默认情况下，分支不是要推送的新更改吗？为什么我需要运行第二个命令？

问为什么我需要显式推送一个新的分支？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问为什么我需要显式推送一个新的分支？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问为什么我需要显式推送一个新的分支？
EN