I want to be able to do the following:

  1. Create a local branch based on some other (remote or local) branch (via git branch or git checkout -b)

  2. Push the local branch to the remote repository (publish), but make it trackable so git pull and git push will work immediately.

How do I do that?

I know about --set-upstream in Git 1.7, but that is a post-creation action. I want to find a way to make a similar change when pushing the branch to the remote repository.

13 Answers 13

up vote 5788 down vote accepted

In Git 1.7.0 and later, you can checkout a new branch:

git checkout -b <branch>

Edit files, add and commit. Then push with the -u (short for --set-upstream) option:

git push -u origin <branch>

Git will set up the tracking information during the push.

  • 46
    It's also worth noting that if you have an existing tracking branch already set on the branch you're pushing, and push.default is set to upstream, this will not do what you think it will do. It will try to push over the existing tracking branch. Use: git push -u origin mynewfeature:mynewfeature or do git branch --unset-upstream first. – void.pointer May 19 '14 at 18:07
  • 1
    I still needed to 'git branch --set-upstream-to origin/remote' in order for 'git status' to correctly report my branch status with respect to the remote branch. – Paul Whipp Jul 4 '14 at 1:17
  • 10
    For people using Git from Visual Studio: Actually this is that "Publish Branch" in Visual Studio does. After executing git push with -u parameter i can finally see my branch as published in VS UI. – Puterdo Borato Mar 19 '15 at 11:19
  • 4
    Do we need the -u option every time we push the branch to its remote or only need it the very first time ? – Stephane Jun 15 '17 at 8:09
  • 5
    @Stephane You only need the -u once to initiate tracking. Afterward just use git push – Todd Jan 11 at 14:49

If you are not sharing your repo with others, this is useful to push all your branches to the remote, and --set-upstream tracking correctly for you:

git push --all -u

(Not exactly what the OP was asking for, but this one-liner is pretty popular)

If you are sharing your repo with others this isn't really good form as you will clog up the repo with all your dodgy experimental branches.

  • 11
    and git pull --all pulls it all back elsewhere ? kewl – commonpike Oct 19 '14 at 21:15
  • This command sets up tracking to the correct branch without the need to push anything. Thank you. – amey91 Jan 21 '15 at 22:03
  • 26
    Git allows to commit a branch and not push it for very good reasons. Only using git push --all is like dropping a piece of git architecture. If it works for you, it is perfectly ok, great, do it forever. But PLEASE don't recommend others to avoid learning git just because it is a quick way to do things. – Federico Razzoli Jul 20 '16 at 8:24
  • 2
    This really isn't the right answer and isn't a good tool to be recommending without a real explanation of what it does and what the implications are. Please consider taking this answer down. – akronymn Jan 31 '17 at 14:30
  • 2
    @Federico @akronymn Where can one find the dangers of doing git push --all -u? – user1823664 Aug 2 '17 at 16:46

Prior to the introduction of git push -u, there was no git push option to obtain what you desire. You had to add new configuration statements.

If you create a new branch using:

$ git checkout -b branchB
$ git push origin branchB:branchB

You can use the git config command to avoid editing directly the .git/config file.

$ git config branch.branchB.remote origin
$ git config branch.branchB.merge refs/heads/branchB

Or you can edit manually the .git/config file to had tracking information to this branch.

[branch "branchB"]
    remote = origin
    merge = refs/heads/branchB
  • sometimes your need this git push origin -u local_branch:remote_branch – Bruce Lee Aug 21 at 6:28

Simply put, to create a new local branch, do:

git branch <branch-name>

To push it to the remote repository, do:

git push -u origin <branch-name>
  • 11
    git branch <branch-name> and git checkout -b <branch-name> both create a branch but checkout switch to the new branch – Robert Aug 11 '16 at 14:37
  • there is no brackets – jairhumberto May 28 at 22:14
  • dude bracket is just to mention you have to replace with whatever branch name you want to create and push. – piyushmandovra May 30 at 3:41

A slight variation of the solutions already given here:

  1. Create a local branch based on some other (remote or local) branch:

    git checkout -b branchname
    
  2. Push the local branch to the remote repository (publish), but make it trackable so git pull and git push will work immediately

    git push -u origin HEAD
    

    Using HEAD is a "handy way to push the current branch to the same name on the remote". Source: https://git-scm.com/docs/git-push In Git terms, HEAD (in uppercase) is a reference to the top of the current branch (tree).

    The -u option is just short for --set-setupstream. This will add an upstream tracking reference for the current branch. you can verify this by looking in your .git/config file:

    Enter image description here

  • 1
    Thank you :) git push -u origin <branch-name> wasn't working for me but using HEAD instead of <branch-name> worked perfectly :) – Daniel Tonon Nov 7 '16 at 7:55
  • This one works for me. The top answer does not work. – jdhao May 8 at 14:52
  • 3
    I love HEAD - too lazy to type ;-) – user776686 Jun 6 at 16:11
  • 2
    @user776686 you have to know what you just did there, right? – Yatrix Jun 7 at 14:16
  • Love this answer - typing "HEAD" is way easier than typing the full name of a (often lengthy or convoluted) feature branch name. – JKubecki Jul 13 at 17:47

I suppose that you have already cloned a project like:

git clone http://github.com/myproject.git
  1. Then in your local copy, create a new branch and check it out:

    git checkout -b <newbranch>
    
  2. Supposing that you made a "git bare --init" on your server and created the myapp.git, you should:

    git remote add origin ssh://example.com/var/git/myapp.git
    git push origin master
    
  3. After that, users should be able to

    git clone http://example.com/var/git/myapp.git
    

NOTE: I'm assuming that you have your server up and running. If it isn't, it won't work. A good how-to is here.

ADDED

Add a remote branch:

git push origin master:new_feature_name

Check if everything is good (fetch origin and list remote branches):

git fetch origin
git branch -r

Create a local branch and track the remote branch:

git checkout -tb new_feature_name origin/new_feature_name

Update everything:

git pull
  • William's script I linked to does about the same with the additional option to delete remote branches and some safeguards, too – Tobias Kienzler May 4 '10 at 13:07
  • >to push the local branch to remote repo (publish), but make it >trackable so git pull and git push will work immediately. its what github does automatically when you push your code to their repository :-) – VP. May 4 '10 at 13:14
  • This does not respond to the question, the <newbranch> of the original repo is not trackable (and is renamed as <master> is the new repo you clone in step 3). – Lohrun May 4 '10 at 13:16
  • seems kind of overkill. does the git remote add origin make the local branch trackable? is that the key command here? – Roni Yaniv May 4 '10 at 13:21
  • 2
    @Roni Yaniv: no git remote add origin only register a new remote repository. It is just a step needed before pushing your branch to that remote repository (if you don't want to type the whole address each time) – Lohrun May 4 '10 at 13:25

I simply do

git push -u origin localBranch:remoteBranchToBeCreated

over an already cloned project.

Git creates a new branch named remoteBranchToBeCreated under my commits I did in localBranch.

edit Outdated, just use git push -u origin $BRANCHNAME


Use git publish-branch from William's miscellaneous Git tools (gitorious repo and clone).

OK, no Ruby, so - ignoring the safeguards! - take the last three lines of the script and create a bash script, git-publish-branch:

#!/bin/bash
REMOTE=$1 # Rewrite this to make it optional...
BRANCH=$2
# Uncomment the following line to create BRANCH locally first
#git checkout -b ${BRANCH}
git push ${ORIGIN} ${BRANCH}:refs/heads/${BRANCH} &&
git config branch.${BRANCH}.remote ${REMOTE} &&
git config branch.${BRANCH}.merge refs/heads/${BRANCH}

Then run git-publish-branch REMOTENAME BRANCHNAME, where REMOTENAME is usually origin (you may modify the script to take origin as default, etc...)

  • this assumes I have ruby installed. no such luck. any other ideas? – Roni Yaniv May 4 '10 at 13:20
  • 1
    the ruby script calls git push and git config command. I used the code of the script to edit my answer. You might used this information to create a small shell script that does the puslishing for you. – Lohrun May 4 '10 at 13:31
  • William's miscellaneous git tools appears to have moved (that link is now dead). A working link is: gitorious.org/willgit – Mike D Oct 27 '14 at 2:08
  • "William's" link broken again; new link seems to be git-wt-commit.rubyforge.org – ScottJ Aug 11 '16 at 1:07

To create a new branch by branching off from existing branch

git checkout -b <new_branch>

and then push this new branch to repository using

git push -u origin <new_branch>

This creates and pushes all local commits to a newly created remote branch origin/<new_branch>

I made an alias so that whenever I create a new branch, it will push and track the remote branch accordingly. I put following chunk into the .bash_profile file:

# Create a new branch, push to origin and track that remote branch
publishBranch() {
  git checkout -b $1
  git push -u origin $1
}
alias gcb=publishBranch

Usage: just type gcb thuy/do-sth-kool with thuy/do-sth-kool is my new branch name.

For GitLab version prior to 1.7, use:

git checkout -b name_branch

(name_branch, ex :master)

To push it to the remote repository, do:

git push -u origin name_new_branch

(name_new_branch, example: feature)

Building slightly upon the answers here, I've wrapped this process up as a simple Bash script, which could of course be used as a Git alias as well.

The important addition to me is that this prompts me to run unit tests before committing and passes in the current branch name by default.

$ git_push_new_branch.sh

  Have you run your unit tests yet? If so, pass OK or a branch name, and try again

  usage: git_push_new_branch {OK|BRANCH_NAME}

  e.g.

  git_push_new_branch           -> Displays prompt reminding you to run unit tests
  git_push_new_branch OK        -> Pushes the current branch as a new branch to the origin
  git_push_new_branch MYBRANCH  -> Pushes branch MYBRANCH as a new branch to the origin

git_push_new_branch.sh

function show_help()
{
  IT=$(CAT <<EOF

  Have you run your unit tests yet? If so, pass OK or a branch name, and try again

  usage: git_push_new_branch {OK|BRANCH_NAME}

  e.g.

  git_push_new_branch.sh           -> Displays prompt reminding you to run unit tests
  git_push_new_branch.sh OK        -> Pushes the current branch as a new branch to the origin
  git_push_new_branch.sh MYBRANCH  -> Pushes branch MYBRANCH as a new branch to the origin

  )
  echo "$IT"
  exit
}

if [ -z "$1" ]
then
  show_help
fi

CURR_BRANCH=$(git rev-parse --abbrev-ref HEAD)
if [ "$1" == "OK" ]
then
  BRANCH=$CURR_BRANCH
else
  BRANCH=${1:-$CURR_BRANCH}
fi

git push -u origin $BRANCH

To upload your local branch of a public repository, you need to cd to the public repository and then use the following code:

git push -u origin branchname
  • 15
    This answer does not add anything to the (plentiful) existing answers and even has some shortcomings (a remote repo does not have to be a public repo). – Dubu Jul 16 '15 at 14:44

protected by Jorgesys Jan 14 '14 at 0:20

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).

Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged or ask your own question.