All Push all branches (i.e.

Atomic Use an atomic transaction on the remote side if available.

Delete All listed refs are deleted from the remote repository.

DryRun Do everything except actually send the updates.

Exec Path to the git-receive-pack program on the remote end.

FollowTags 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.

Force Usually, the command refuses to update a remote ref that is not an ancestor of the local ref used to overwrite it.

ForceWithLease alone, without specifying the details, will protect all remote refs that are going to be updated by requiring their current value to be the same as the remote-tracking branch we have for them.

ForceWithLeaseExpect will protect the named ref (alone), if it is going to be updated, by requiring its current value to be the same as the specified value <expect> (which is allowed to be different from the remote-tracking branch we have for the refname, or we do not even have to have such a remote-tracking branch when this form is used).

ForceWithLeaseRef without specifying the expected value, will protect the named ref (alone), if it is going to be updated, by requiring its current value to be the same as the remote-tracking branch we have for it.

Ipv4 Use IPv4 addresses only, ignoring IPv6 addresses.

Ipv6 Use IPv6 addresses only, ignoring IPv4 addresses.

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.

NoAtomic Use an atomic transaction on the remote side if available.

NoFollowTags undocumented push option --no-follow-tags.

NoForceWithLease Usually, "git push" refuses to update a remote ref that is not an ancestor of the local ref used to overwrite it.

NoRecurseSubmodules May be used to make sure all submodule commits used by the revisions to be pushed are available on a remote-tracking branch.

NoSigned 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.

NoThin These options are passed to git-send-pack(1).

NoVerify Toggle the pre-push hook (see githooks(5)).

Porcelain Produce machine-readable output.

Progress Progress status is reported on the standard error stream by default when it is attached to a terminal, unless -q is specified.

Prune Remove remote branches that don’t have a local counterpart.

PushOption Transmit the given string to the server, which passes them to the pre-receive as well as the post-receive hook.

Quiet Suppress all output, including the listing of updated refs, unless an error occurs.

ReceivePack Path to the git-receive-pack program on the remote end.

RecurseSubmodules May be used to make sure all submodule commits used by the revisions to be pushed are available on a remote-tracking branch.

RefSpec Specify what destination ref to update with what source object.

Remote The "remote" repository that is destination of a push operation.

Repo This option is equivalent to the <repository> argument.

SetUpstream 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.

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.

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.

Tags All refs under refs/tags are pushed, in addition to refspecs explicitly listed on the command line.

Thin These options are passed to git-send-pack(1).

Verbose Run verbosely.

Verify Toggle the pre-push hook (see githooks(5)).