Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

push master, or push all?

Hi, a newbie question: Following the instruction on how to set up a local repo and then get it over to Bitbucket, I think I managed to successfully do the command:

$ git push -u origin master

That 's the last of two commands I pasted from the Bitbucket Overview page. But maybe I should only have done the 'remote add origin' thing (the first command)?

Then , the instruction says I should do:

$ git push -u origin --all

But is this necessary? Do I really need to push twice? I don't know the difference between "master" and "all". Tell me if I did anything wrong here.

2 answers

1 accepted

1 vote
Answer accepted

The instructions on the overview page assume you are only pushing one branch, master.  If you have a repo that contains many branches then you need to push the all with the 'git push --mirror origin' to push all refs under refs/ (which may include but is not limited to refs/heads/, refs/remotes/, and refs/tags/). See the documentation for git push for other options.  For example you could also do a 'git push --all origin' to push just branches and not tags.

Thank you very much! No, what I'm aware of there is only one branch. A "branch" is something you can create, when already working with Git, or Mercurial, e.g. to be able to experiment with some creative idea that you're kind of unsure of?


With one branch 'git push -u origin master' will work just fine assuming the one branch you are referring to is the master branch.  Branches are used for many things.  They can be used to isolate experimental work as you describe. They can be used for implementing bugfixes, new features, releases, etc.  There are a number of resources online that describe various git branch strategies.  Here is a link from Atlassian's site: but there are many more.


Please look at

So, -u is connect you local branch master to remote branch origin/master after push.

If you use --all, then all local branches will pushed on server.

After your local branch is connected to remote branch, you can simple use git push, without specification remote and branch. It will push current branch into connected remote branch.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bitbucket

New improvements to user management in Bitbucket Cloud 👥

Hey Community! We’re willing to wager that quite a few of you not only use Bitbucket, but administer it too. Our team is excited to share that we’ll be releasing improvements throughout this month of...

3,927 views 10 16
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you