search

Home  >  Q&A  >  body text

git - warning: push.default is unset , simple or matching ?

Use git push to remote, but this error message appears warning: push.default is unset
Should I choose simple or matching?

ben:basic sl$ git push
warning: push.default is unset; its implicit value has changed in
Git 2.0 from 'matching' to 'simple'. To squelch this message
and maintain the traditional behavior, 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.

Since Git 2.0, Git defaults 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)
曾经蜡笔没有小新曾经蜡笔没有小新2793 days ago736

reply all(1)I'll reply

  • 世界只因有你

    世界只因有你2017-05-02 09:26:13

    The 'matching' parameter is the default behavior of Git 1.x, which means that if you execute git push without specifying a branch, it will push all your local branches to the corresponding matching branches in the remote repository. The default for Git 2.x is simple, which means that when executing git push without specifying a branch, only the current branch will be pushed to the code you obtained using git pull.
    According to the prompts, modify the behavior of git push so that it will not prompt every time you push
    git config --global push.default matching
    Execute git push again

    reply
    0
  • Cancelreply