Git : git push matching vs simple

A partir de la version 2 :

warning: push.default is unset; its implicit value is changing in 
Git 2.0 from 'matching to 'simple'. To squelch this message and 
maintain the current behavior after the default changes, use:

   git config -- global push.default matching

To squelch this message and adopt the new behavior now, use:

  git config --global push.default simple

When push.default is set to 'matching', git will push local branches 
to the remote branches that already exist with the same name.

In Git 2.0, Git will default to the more conservative 'simple' behavior, 
which only pushes the current branch to the corresponding remote 
branch that 'git pull' uses to update the current branch.

See 'git help config' and search for 'push.default' for further information. 
(the 'simple' mode was introduced in Git 1.7.11. Use the similar mode 
'current' instead of 'simple' if you sometimes use older versions of Git)

In short, matching forces you to keep remote and local branches in sync, with the same names at all time. Simple lets you have different branch names and doesn’t force you to push all the branches as the same time. For me simple is a lot more, er, simpler, and safe and reflects the way I work better. The choice is easy.

 git config --global push.default simple 

utiliser 

git push -u origin branch : pour la premier fois afin que git fait le set du remote en tant que upstream (l'option -u)