Warning: push.default is unset; its implicit value is changing in Git 2.0

Here is what can be found under push.default in the documentation:

  • current – push the current branch to update a branch with the same name on the receiving end. Works in both central and non-central workflows.
  • upstream – push the current branch back to the branch whose changes are usually integrated into the current branch (which is called @{upstream}). This mode only makes sense if you are pushing to the same repository you would normally pull from (i.e. central workflow).
  • simple – in centralized workflow, work like upstream with an added safety to refuse to push if the upstream branch’s name is different from the local one. When pushing to a remote that is different from the remote you normally pull from, work as current. This is the safest option and is suited for beginners. This mode has become the default in Git 2.0.
  • matching – push all branches having the same name on both ends. This makes the repository you are pushing to remember the set of branches that will be pushed out (e.g. if you always push maint and master there and no other branches, the repository you push to will have these two branches, and your local maint and master will be pushed there). Default before Git 2.0.

I chose to use simple by using the suggested command:

git config --global push.default simple

 

Leave a Comment