I use the following command to push to my remote branch:
git push origin sandbox
If I say
git push origin
does that push changes in my other branches too, or does it only update my current branch? I have three branches: master, production and sandbox.
The git push documentation is not very clear about this, so I'd like to clarify this for good.
Which branches and remotes do the following git push commands update exactly?
git push
git push origin
origin above is a remote.
I understand that git push [remote] [branch] will push only that branch to the remote.
This question is related to
git
branch
git-branch
git-push
I just committed my code to a branch and pushed it to github, like this:
git branch SimonLowMemoryExperiments
git checkout SimonLowMemoryExperiments
git add .
git commit -a -m "Lots of experimentation with identifying the memory problems"
git push origin SimonLowMemoryExperiments
I just put this in my .gitconfig aliases section and love how it works:
pub = "!f() { git push -u ${1:-origin} `git symbolic-ref HEAD`; }; f"
Will push the current branch to origin with git pub or another repo with git pub repo-name. Tasty.
A git push will try and push all local branches to the remote server, this is likely what you do not want. I have a couple of conveniences setup to deal with this:
Alias "gpull" and "gpush" appropriately:
In my ~/.bash_profile
get_git_branch() {
echo `git branch 2> /dev/null | sed -e '/^[^*]/d' -e 's/* \(.*\)/\1/'`
}
alias gpull='git pull origin `get_git_branch`'
alias gpush='git push origin `get_git_branch`'
Thus, executing "gpush" or "gpull" will push just my "currently on" branch.
git push origin will push all changes on the local branches that have matching remote branches at origin As for git push
Works like
git push <remote>, where<remote>is the current branch's remote (or origin, if no remote is configured for the current branch).
From the Examples section of the git-push man page
Rather than using aliases, I prefer creating git-XXX scripts so I can source control them more easily (our devs all have a certain source controlled dir on their path for this type of thing).
This script (called git-setpush) will set the config value for remote.origin.push value to something that will only push the current branch:
#!/bin/bash -eu
CURRENT_BRANCH=$(git branch | grep '^\*' | cut -d" " -f2)
NEW_PUSH_REF=HEAD:refs/for/$CURRENT_BRANCH
echo "setting remote.origin.push to $NEW_PUSH_REF"
git config remote.origin.push $NEW_PUSH_REF
note, as we're using Gerrit, it sets the target to refs/for/XXX to push into a review branch. It also assumes origin is your remote name.
Invoke it after checking out a branch with
git checkout your-branch
git setpush
It could obviously be adapted to also do the checkout, but I like scripts to do one thing and do it well
You can change that default behavior in your .gitconfig, for example:
[push]
default = current
To check the current settings, run:
git config --global --get push.default
Here is a very handy and helpful information about Git Push: Git Push: Just the Tip
The most common use of git push is to push your local changes to your public upstream repository. Assuming that the upstream is a remote named "origin" (the default remote name if your repository is a clone) and the branch to be updated to/from is named "master" (the default branch name), this is done with: git push origin master
git push origin will push changes from all local branches to matching branches the origin remote.
git push origin master will push changes from the local master branch to the remote master branch.
git push origin master:staging will push changes from the local master branch to the remote staging branch if it exists.
You can set up default behavior for your git with push.default
git config push.default current
or if you have many repositories and want the same for all then
git config --global push.default current
The current in this setup means that by default you will only push the current branch when you do git push
Other options are:
UPDATE - NEW WAY TO DO THIS
As of Git 1.7.11 do the following:
git config --global push.default simple
This is a new setting introduced that works in the same way as current, and will be made default to git from v 2.0 according to rumors
I have added the following functions into my .bashrc file to automate these tasks. It does git push/git pull + name of current branch.
function gpush()
{
if [[ "x$1" == "x-h" ]]; then
cat <<EOF
Usage: gpush
git: for current branch: push changes to remote branch;
EOF
else
set -x
local bname=`git rev-parse --abbrev-ref --symbolic-full-name @{u} | sed -e "s#/# #"`
git push ${bname}
set +x
fi
}
function gpull()
{
if [[ "x$1" == "x-h" ]]; then
cat <<EOF
Usage: gpull
git: for current branch: pull changes from
EOF
else
set -x
local bname=`git rev-parse --abbrev-ref --symbolic-full-name @{u} | sed -e "s#/# #"`
git pull ${bname}
set +x
fi
}
(March 2012)
Beware: that default "matching" policy might change soon
(sometimes after git1.7.10+):
See "Please discuss: what "git push" should do when you do not say what to push?"
In the current setting (i.e.
push.default=matching),git pushwithout argument will push all branches that exist locally and remotely with the same name.
This is usually appropriate when a developer pushes to his own public repository, but may be confusing if not dangerous when using a shared repository.The proposal is to change the default to '
upstream', i.e. push only the current branch, and push it to the branch git pull would pull from.
Another candidate is 'current'; this pushes only the current branch to the remote branch of the same name.What has been discussed so far can be seen in this thread:
http://thread.gmane.org/gmane.comp.version-control.git/192547/focus=192694
Previous relevant discussions include:
To join the discussion, send your messages to: [email protected]
Source: Stackoverflow.com