Text of git-scm.com › docs › git-push › 2.15.4 as Styx crawled it on Oct 13, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

Git - git-push Documentation

English ▾ English Français Português (Brasil) Русский Svenska українська мова 简体中文 Topics ▾ Setup and Config git config help bugreport Credential helpers Getting and Creating Projects init clone Basic Snapshotting add status diff commit notes restore reset rm mv Branching and Merging branch checkout switch merge mergetool log stash tag worktree Sharing and Updating Projects fetch pull push remote submodule Inspection and Comparison show log diff difftool range-diff shortlog describe Patching apply cherry-pick diff rebase revert Debugging bisect blame grep Email am apply imap-send format-patch send-email request-pull External Systems svn fast-import Server Admin daemon update-server-info Guides gitattributes Command-line interface conventions Everyday Git Frequently Asked Questions (FAQ) Glossary Hooks gitignore gitmodules Revisions Submodules Tutorial Workflows All guides...

Administration clean gc fsck reflog filter-branch instaweb archive bundle Plumbing Commands cat-file check-ignore checkout-index commit-tree count-objects diff-index for-each-ref hash-object ls-files ls-tree merge-base read-tree rev-list rev-parse show-ref symbolic-ref update-index update-ref verify-pack write-tree Version 2.15.4 ▾ git-push last updated in 2.55.0 2.56.0 no changes 2.55.0 2026-06-29 2.54.0 no changes 2.53.0 2026-02-02 2.52.0 2025-11-17 2.48.1 → 2.51.2 no changes 2.48.0 2025-01-10 2.45.1 → 2.47.3 no changes 2.45.0 2024-04-29 2.44.1 → 2.44.4 no changes 2.44.0 2024-02-23 2.43.1 → 2.43.7 no changes 2.43.0 2023-11-20 2.42.2 → 2.42.4 no changes 2.42.1 2023-11-02 2.42.0 2023-08-21 2.41.1 → 2.41.3 no changes 2.41.0 2023-06-01 2.40.1 → 2.40.4 no changes 2.40.0 2023-03-12 2.39.1 → 2.39.5 no changes 2.39.0 2022-12-12 2.38.1 → 2.38.5 no changes 2.38.0 2022-10-02 2.35.1 → 2.37.7 no changes 2.35.0 2022-01-24 2.33.1 → 2.34.8 no changes 2.33.0 2021-08-16 2.32.1 → 2.32.7 no changes 2.32.0 2021-06-06 2.30.1 → 2.31.8 no changes 2.30.0 2020-12-27 2.25.1 → 2.29.3 no changes 2.25.0 2020-01-13 2.23.1 → 2.24.4 no changes 2.23.0 2019-08-16 2.22.1 → 2.22.5 no changes 2.22.0 2019-06-07 2.21.1 → 2.21.4 no changes 2.21.0 2019-02-24 2.20.1 → 2.20.5 no changes 2.20.0 2018-12-09 2.18.1 → 2.19.6 no changes 2.18.0 2018-06-21 2.17.0 → 2.17.6 no changes 2.16.6 2019-12-06 2.15.4 2019-12-06 2.14.6 no changes 2.13.7 2018-05-22 2.12.5 2017-09-22 2.11.4 2017-09-22 2.10.5 2017-09-22 2.9.5 2017-07-30 2.8.6 2017-07-30 2.7.6 2017-07-30 2.6.7 2017-05-05 2.5.6 no changes 2.4.12 2017-05-05 2.3.10 2015-09-28 2.2.3 2015-09-04 2.1.4 no changes 2.0.5 2014-12-17 NAME git-push - Update remote refs along with associated objects SYNOPSIS git push [--all | --mirror | --tags] [--follow-tags] [--atomic] [-n | --dry-run] [--receive-pack=<git-receive-pack>] [--repo= <repository> ] [-f | --force] [-d | --delete] [--prune] [-v | --verbose] [-u | --set-upstream] [--push-option=<string>] [--[no-]signed|--signed=(true|false|if-asked)] [--force-with-lease[=<refname>[:<expect>]]] [--no-verify] [ <repository> [ <refspec> …​]] DESCRIPTION Updates remote refs using local refs, while sending objects necessary to complete the given refs.

You can make interesting things happen to a repository every time you push into it, by setting up hooks there. See documentation for git-receive-pack[1] . When the command line does not specify where to push with the <repository> argument, branch.*.remote configuration for the current branch is consulted to determine where to push. If the configuration is missing, it defaults to origin . When the command line does not specify what to push with <refspec> ... arguments or --all , --mirror , --tags options, the command finds the default <refspec> by consulting remote.*.push configuration, and if it is not found, honors push.default configuration to decide what to push (See git-config[1] for the meaning of push.default ).

When neither the command-line nor the configuration specify what to push, the default behavior is used, which corresponds to the simple value for push.default : the current branch is pushed to the corresponding upstream branch, but as a safety measure, the push is aborted if the upstream branch does not have the same name as the local one. OPTIONS <repository> The "remote" repository that is destination of a push operation.

This parameter can be either a URL (see the section GIT URLS below) or the name of a remote (see the section REMOTES below). <refspec> …​ Specify what destination ref to update with what source object. The format of a <refspec> parameter is an optional plus + , followed by the source object <src>, followed by a colon : , followed by the destination ref <dst>. The <src> is often the name of the branch you would want to push, but it can be any arbitrary "SHA-1 expression", such as master~4 or HEAD (see gitrevisions[7] ).

The <dst> tells which ref on the remote side is updated with this push. Arbitrary expressions cannot be used here, an actual ref must be named. If git push [ <repository> ] without any <refspec> argument is set to update some ref at the destination with <src> with remote. <repository> .push configuration variable, : <dst> part can be omitted—​such a push will update a ref that <src> normally updates without any <refspec> on the command line.

Otherwise, missing : <dst> means to update the same ref as the <src> . The object referenced by <src> is used to update the <dst> reference on the remote side. By default this is only allowed if <dst> is not a tag (annotated or lightweight), and then only if it can fast-forward <dst>. By having the optional leading + , you can tell Git to update the <dst> ref even if it is not allowed by default (e.g., it is not a fast-forward.) This does not attempt to merge <src> into <dst>.

See EXAMPLES below for details. tag <tag> means the same as refs/tags/ <tag> :refs/tags/ <tag> . Pushing an empty <src> allows you to delete the <dst> ref from the remote repository. The special refspec : (or +: to allow non-fast-forward updates) directs Git to push "matching" branches: for every branch that exists on the local side, the remote side is updated if a branch of the same name already exists on the remote side. --all Push all branches (i.e. refs under refs/heads/ ); cannot be used with other <refspec> . --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. --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. <remote> .mirror is set. -n --dry-run Do everything except actually send the updates. --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. --delete All listed refs are deleted from the remote repository. This is the same as prefixing all refs with a colon. --tags All refs under refs/tags are pushed, in addition to refspecs explicitly listed on the command line. --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] . --[no-]signed --si

The rest of this page is on the live site.