Why do I have to git push --set-upstream origin branch

Question

I created a local branch for testing Solaris and Sun Studio  I then pushed the branch upstream  After committing a change and attempting to push the changes     git commit blake2 cpp -m  Add workaround for missing  mm set epi64x   solaris 7ad22ff  Add workaround for missing  mm set epi64x  1 file changed  5 insertions      git push fatal  The current branch solaris has no upstream branch  To push the current branch and set the remote as upstream  use      git push --set-upstream origin solaris   Why do I have to do something special for this   Is there any reasonable use case where someone would create  lt branch gt   push the  lt branch gt  to remote  and then claim a commit on  lt branch gt  is not supposed to be for  lt branch gt      I followed this question and answer on Stack Overflow  Push a new local branch to a remote Git repository and track it too  I m guessing its another instance of a incomplete or wrong accepted answer  Or  its another instance of Git taking a simple task and making it difficult     Here s the view on a different machine  The branch clearly exists  so it was created and pushed     git branch -a   alignas   master   remotes origin HEAD - gt  origin master   remotes origin alignas   remotes origin arm-neon   remotes origin det-sig   remotes origin master   remotes origin solaris

User · Answer

My understanding is that  quot -u quot  or  quot --set-upstream quot  allows you to specify the upstream  remote  repository for the branch you re on  so that next time you run  quot git push quot   you don t even have to specify the remote repository  Push and set upstream  remote  repository as origin    git push -u origin  Next time you push  you don t have to specify the remote repository    git push

User · Answer

The -u flag is specifying that you want to link your local branch to the upstream branch  This will also create an upstream branch if one does not exist  None of these answers cover how i do it  in complete form  so here it is  git push -u origin  lt your-local-branch-name gt   So if your local branch name is coffee git push -u origin coffee

User · Answer

TL DR  git branch --set-upstream-to origin solaris    The answer to the question you asked   which I ll rephrase a bit as  do I have to set an upstream    is  no  you don t have to set an upstream at all   If you do not have upstream for the current branch  however  Git changes its behavior on git push  and on other commands as well   The complete push story here is long and boring and goes back in history to before Git version 1 5   To shorten it a whole lot  git push was implemented poorly 1  As of Git version 2 0  Git now has a configuration knob spelled push default which now defaults to simple   For several versions of Git before and after 2 0  every time you ran git push  Git would spew lots of noise trying to convince you to set push default just to get git push to shut up   You do not mention which version of Git you are running  nor whether you have configured push default  so we must guess   My guess is that you are using Git version 2-point-something  and that you have set push default to simple to get it to shut up   Precisely which version of Git you have  and what if anything you have push default set to  does matter  due to that long and boring history  but in the end  the fact that you re getting yet another complaint from Git indicates that your Git is configured to avoid one of the mistakes from the past   What is an upstream   An upstream is simply another branch name  usually a remote-tracking branch  associated with a  regular  local  branch   Every branch has the option of having one  1  upstream set   That is  every branch either has an upstream  or does not have an upstream   No branch can have more than one upstream   The upstream should  but does not have to be  a valid branch  whether remote-tracking like origin B or local like master    That is  if the current branch B has upstream U  git rev-parse U should work   If it does not work   if it complains that U does not exist   then most of Git acts as though the upstream is not set at all   A few commands  like git branch -vv  will show the upstream setting but mark it as  gone    What good is an upstream   If your push default is set to simple or upstream  the upstream setting will make git push  used with no additional arguments  just work   That s it   that s all it does for git push   But that s fairly significant  since git push is one of the places where a simple typo causes major headaches   If your push default is set to nothing  matching  or current  setting an upstream does nothing at all for git push    All of this assumes your Git version is at least 2 0    The upstream affects git fetch  If you run git fetch with no additional arguments  Git figures out which remote to fetch from by consulting the current branch s upstream   If the upstream is a remote-tracking branch  Git fetches from that remote    If the upstream is not set or is a local branch  Git tries fetching origin    The upstream affects git merge and git rebase too  If you run git merge or git rebase with no additional arguments  Git uses the current branch s upstream   So it shortens the use of these two commands   The upstream affects git pull  You should never2 use git pull anyway  but if you do  git pull uses the upstream setting to figure out which remote to fetch from  and then which branch to merge or rebase with   That is  git pull does the same thing as git fetch   because it actually runs git fetch   and then does the same thing as git merge or git rebase  because it actually runs git merge or git rebase    You should usually just do these two steps manually  at least until you know Git well enough that when either step fails  which they will eventually  you recognize what went wrong and know what to do about it    The upstream affects git status  This may actually be the most important   Once you have an upstream set  git status can report the difference between your current branch and its upstream  in terms of commits   If  as is the normal case  you are on branch B with its upstream set to origin B  and you run git status  you will immediately see whether you have commits you can push  and or commits you can merge or rebase onto   This is because git status runs    git rev-list --count   u   HEAD  how many commits do you have on B that are not on origin B  git rev-list --count HEAD    u   how many commits do you have on origin B that are not on B    Setting an upstream gives you all of these things   How come master already has an upstream set   When you first clone from some remote  using     git clone git   some host path to repo git   or similar  the last step Git does is  essentially  git checkout master   This checks out your local branch master   only you don t have a local branch master   On the other hand  you do have a remote-tracking branch named origin master  because you just cloned it   Git guesses that you must have meant   make me a new local master that points to the same commit as remote-tracking origin master  and  while you re at it  set the upstream for master to origin master    This happens for every branch you git checkout that you do not already have   Git creates the branch and makes it  track   have as an upstream  the corresponding remote-tracking branch   But this doesn t work for new branches  i e   branches with no remote-tracking branch yet   If you create a new branch     git checkout -b solaris   there is  as yet  no origin solaris   Your local solaris cannot track remote-tracking branch origin solaris because it does not exist   When you first push the new branch     git push origin solaris   that creates solaris on origin  and hence also creates origin solaris in your own Git repository   But it s too late  you already have a local solaris that has no upstream 3  Shouldn t Git just set that  now  as the upstream automatically   Probably   See  implemented poorly  and footnote 1   It s hard to change now  There are millions4 of scripts that use Git and some may well depend on its current behavior   Changing the behavior requires a new major release  nag-ware to force you to set some configuration field  and so on   In short  Git is a victim of its own success  whatever mistakes it has in it  today  can only be fixed if the change is either mostly invisible  clearly-much-better  or done slowly over time   The fact is  it doesn t today  unless you use --set-upstream or -u during the git push   That s what the message is telling you   You don t have to do it like that   Well  as we noted above  you don t have to do it at all  but let s say you want an upstream   You have already created branch solaris on origin  through an earlier push  and as your git branch output shows  you already have origin solaris in your local repository   You just don t have it set as the upstream for solaris   To set it now  rather than during the first push  use git branch --set-upstream-to   The --set-upstream-to sub-command takes the name of any existing branch  such as origin solaris  and sets the current branch s upstream to that other branch   That s it   that s all it does   but it has all those implications noted above   It means you can just run git fetch  then look around  then run git merge or git rebase as appropriate  then make new commits and run git push  without a bunch of additional fussing-around     1To be fair  it was not clear back then that the initial implementation was error-prone   That only became clear when every new user made the same mistakes every time   It s now  less poor   which is not to say  great    2 Never  is a bit strong  but I find that Git newbies understand things a lot better when I separate out the steps  especially when I can show them what git fetch actually did  and they can then see what git merge or git rebase will do next   3If you run your first git push as git push -u origin solaris   i e   if you add the -u flag   Git will set origin solaris as the upstream for your current branch if  and only if  the push succeeds   So you should supply -u on the first push   In fact  you can supply it on any later push  and it will set or change the upstream at that point   But I think git branch --set-upstream-to is easier  if you forgot   4Measured by the Austin Powers   Dr Evil method of simply saying  one MILLLL-YUN   anyway

User · Answer

If you forgot to add the repository HTTPS link then put it with git push  lt repo HTTPS gt

User · Answer

A basically full command is like git push  lt remote gt   lt local ref gt   lt remote ref gt   If you run just git push  git does not know what to do exactly unless you have made some config that helps git to make a decision  In a git repo  we can setup multiple remotes  Also we can push a local ref to any remote ref  The full command is the most straightforward way to  make a push  If you want to type fewer words  you have to config first  like --set-upstream

User · Answer

The difference between git push origin  lt branch gt   and git push --set-upstream origin  lt branch gt  is that they both push just fine to the remote repository  but it s when you pull that you notice the difference     If you do  git push origin  lt branch gt  when pulling  you have to do  git pull origin  lt branch gt   But if you do  git push --set-upstream origin  lt branch gt  then  when pulling  you only have to do  git pull  So adding in the --set-upstream allows for not having to specify which branch that you want to pull from every single time that you do git pull

[git] Why do I have to "git push --set-upstream origin <branch>"?

Examples related to git

Examples related to branch