Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>You can control the default behavior by setting push.default in your git config. From <a href="http://git-scm.com/docs/git-config" rel="noreferrer">the git-config(1) documentation</a>:</p> <pre><code>push.default </code></pre> <p>Defines the action git push should take if no refspec is given on the command line, no refspec is configured in the remote, and no refspec is implied by any of the options given on the command line. Possible values are:</p> <ul> <li><p><code>nothing</code>: do not push anything</p></li> <li><p><code>matching</code>: push all matching branches</p> <p>All branches having the same name in both ends are considered to be matching.</p> <p>This is the default in Git 1.x.</p></li> <li><p><code>upstream</code>: push the current branch to its upstream branch (<code>tracking</code> is a deprecated synonym for upstream)</p></li> <li><p><code>current</code>: push the current branch to a branch of the same name</p></li> <li><p><code>simple</code>: (new in Git 1.7.11) like upstream, but refuses to push if the upstream branch's name is different from the local one</p> <p>This is the safest option and is well-suited for beginners.</p> <p>This will become the default in Git 2.0.</p></li> </ul> <blockquote> <p>The simple, current and upstream modes are for those who want to push out a single branch after finishing work, even when the other branches are not yet ready to be pushed out</p> </blockquote> <p>Command line examples:</p> <p>To view the current configuration:</p> <pre><code>git config --global push.default </code></pre> <p>To set a new configuration:</p> <pre><code>git config --global push.default current </code></pre>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload