Module push

Functions

• all
  Push all branches (i.e. refs under refs/heads/); cannot be used with other . –all
• atomic
  Use an atomic transaction on the remote side if available. Either all refs are updated, or on error, no refs are updated. If the server does not support atomic pushes the push will fail. –atomic
• delete
  All listed refs are deleted from the remote repository. This is the same as prefixing all refs with a colon. –delete
• dry_run
  Do everything except actually send the updates. -n, –dry-run
• exec
  Path to the git-receive-pack program on the remote end. Sometimes useful when pushing to a remote repository over ssh, and you do not have the program in a directory on the default $PATH. –exec=
• follow_tags
  Push all the refs that would be pushed without this option, and also push annotated tags in refs/tags that are missing from the remote but are pointing at commit-ish that are reachable from the refs being pushed. This can also be specified with configuration variable push.followTags. For more information, see push.followTags in git-config(1). –follow-tags
• force
  Usually, the command refuses to update a remote ref that is not an ancestor of the local ref used to overwrite it. Also, when –force-with-lease option is used, the command refuses to update a remote ref whose current value does not match what is expected. -f, –force
• ipv4
  Use IPv4 addresses only, ignoring IPv6 addresses. -4, –ipv4
• ipv6
  Use IPv6 addresses only, ignoring IPv4 addresses. -6, –ipv6
• mirror
  Instead of naming each ref to push, specifies that all refs under refs/ (which includes but is not limited to refs/heads/, refs/remotes/, and refs/tags/) be mirrored to the remote repository. Newly created local refs will be pushed to the remote end, locally updated refs will be force updated on the remote end, and deleted refs will be removed from the remote end. This is the default if the configuration option remote..mirror is set. –mirror
• no_atomic
  Use an atomic transaction on the remote side if available. Either all refs are updated, or on error, no refs are updated. If the server does not support atomic pushes the push will fail. –no-atomic
• no_recurse_submodules
  May be used to make sure all submodule commits used by the revisions to be pushed are available on a remote-tracking branch. If check is used Git will verify that all submodule commits that changed in the revisions to be pushed are available on at least one remote of the submodule. If any commits are missing the push will be aborted and exit with non-zero status. If on-demand is used all submodules that changed in the revisions to be pushed will be pushed. If on-demand was not able to push all necessary revisions it will also be aborted and exit with non-zero status. If only is used all submodules will be recursively pushed while the superproject is left unpushed. A value of no or using –no-recurse-submodules can be used to override the push.recurseSubmodules configuration variable when no submodule recursion is required. –no-recurse-submodules
• no_signed
  GPG-sign the push request to update refs on the receiving side, to allow it to be checked by the hooks and/or be logged. If false or –no-signed, no signing will be attempted. If true or –signed, the push will fail if the server does not support signed pushes. If set to if-asked, sign if and only if the server supports signed pushes. The push will also fail if the actual call to gpg –sign fails. See git-receive-pack(1) for the details on the receiving end. –no-signed
• no_thin
  These options are passed to git-send-pack(1). A thin transfer significantly reduces the amount of sent data when the sender and receiver share many of the same objects in common. The default is –thin. –no-thin
• no_verify
  Toggle the pre-push hook (see githooks(5)). The default is –verify, giving the hook a chance to prevent the push. With –no-verify, the hook is bypassed completely. –no-verify
• porcelain
  Produce machine-readable output. The output status line for each ref will be tab-separated and sent to stdout instead of stderr. The full symbolic names of the refs will be given. –porcelain
• progress
  Progress status is reported on the standard error stream by default when it is attached to a terminal, unless -q is specified. This flag forces progress status even if the standard error stream is not directed to a terminal. –progress
• prune
  Remove remote branches that don’t have a local counterpart. For example a remote branch tmp will be removed if a local branch with the same name doesn’t exist any more. This also respects refspecs, e.g. git push –prune remote refs/heads/:refs/tmp/ would make sure that remote refs/tmp/foo will be removed if refs/heads/foo doesn’t exist. –prune
• push
• push_option
  Transmit the given string to the server, which passes them to the pre-receive as well as the post-receive hook. The given string must not contain a NUL or LF character. -o, –push-option
• quiet
  Suppress all output, including the listing of updated refs, unless an error occurs. Progress is not reported to the standard error stream. -q, –quiet
• receive_pack
  Path to the git-receive-pack program on the remote end. Sometimes useful when pushing to a remote repository over ssh, and you do not have the program in a directory on the default $PATH. –receive-pack=
• recurse_submodules
  May be used to make sure all submodule commits used by the revisions to be pushed are available on a remote-tracking branch. If check is used Git will verify that all submodule commits that changed in the revisions to be pushed are available on at least one remote of the submodule. If any commits are missing the push will be aborted and exit with non-zero status. If on-demand is used all submodules that changed in the revisions to be pushed will be pushed. If on-demand was not able to push all necessary revisions it will also be aborted and exit with non-zero status. If only is used all submodules will be recursively pushed while the superproject is left unpushed. A value of no or using –no-recurse-submodules can be used to override the push.recurseSubmodules configuration variable when no submodule recursion is required. –recurse-submodules=(check|on-demand|only|no)
• repo
  This option is equivalent to the argument. If both are specified, the command-line argument takes precedence. –repo=
• set_upstream
  For every branch that is up to date or successfully pushed, add upstream (tracking) reference, used by argument-less git-pull(1) and other commands. For more information, see branch..merge in git-config(1). -u, –set-upstream
• sign
  GPG-sign the push request to update refs on the receiving side, to allow it to be checked by the hooks and/or be logged. If false or –no-signed, no signing will be attempted. If true or –signed, the push will fail if the server does not support signed pushes. If set to if-asked, sign if and only if the server supports signed pushes. The push will also fail if the actual call to gpg –sign fails. See git-receive-pack(1) for the details on the receiving end. –sign=(true|false|if-asked)
• signed
  GPG-sign the push request to update refs on the receiving side, to allow it to be checked by the hooks and/or be logged. If false or –no-signed, no signing will be attempted. If true or –signed, the push will fail if the server does not support signed pushes. If set to if-asked, sign if and only if the server supports signed pushes. The push will also fail if the actual call to gpg –sign fails. See git-receive-pack(1) for the details on the receiving end. –signed
• tags
  All refs under refs/tags are pushed, in addition to refspecs explicitly listed on the command line. –tags
• thin
  These options are passed to git-send-pack(1). A thin transfer significantly reduces the amount of sent data when the sender and receiver share many of the same objects in common. The default is –thin. –thin
• verbose
  Run verbosely. -v, –verbose
• verify
  Toggle the pre-push hook (see githooks(5)). The default is –verify, giving the hook a chance to prevent the push. With –no-verify, the hook is bypassed completely. –verify