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

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: https://www.atlassian.com/git/tutorials/comparing-workflows/ but there are many more.

Hello,

Please look at https://git-scm.com/book/en/ch2-5.html#Pushing-to-Your-Remotes

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
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda&nbsp...

2,047 views 1 5
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you