ATTENTION! While this answer has the most votes and is technically correct, it suggests that the problem is the push.default
option, when usually the real problem is an unintended mismatch between the names of the local branch and the upstream branch. blindly following the instructions in this answer may cause your changes to be pushed to the wrong branch! For a safe quick fix, please see https://stackoverflow.com/a/24865780/2279059 instead.
For the benefit of the readers who might miss the probably most important detail, well hidden in the comments:
This is due to the git config push.default
setting. It defines what git
does when you enter git push
(see link).
In the question, apparently the setting was set to simple
(which is the default for git v2
), probably with
git config --global push.default simple
This means, that git
refuses to push when the local and remote branch do not match exactly.
As @TomSpurling notes, above setting is safer and recommended for normal use,
because usually you want the same names for your local and remote branches.
However in certain situations, when your local branch is tracking some
different remote branch with a different name, then you want to change that:
To allow to push to the tracking branch on a per-git basis, thus make git pull
and git push
symmetric, use
git config push.default upstream
Note: To globally set this for all of your git
s, use git config --global push.default upstream
However it is probably better to leave it to git config --global push.default simple
and only set this option in those workloads, where it is really required.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…