GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||
GeezerVison is showing git-scm.com — Git - git-push Documentation
English ▾
Topics ▾
Setup and ConfigGetting and Creating ProjectsBasic SnapshottingBranching and MergingSharing and Updating ProjectsInspection and ComparisonPatchingDebuggingExternal SystemsServer AdminGuides
AdministrationPlumbing Commands
SYNOPSIS
DESCRIPTIONUpdates one or more branches, tags, or other references in one or more remote repositories from your local repository, and sends all necessary data that isn’t already on the remote. The simplest way to push is You can also push to multiple remotes at once by using a remote group.
A remote group is a named list of remotes configured via $ git config remotes.all-remotes "origin gitlab backup" Then The <repository> argument defaults to the upstream for the current
branch, or To decide which branches, tags, or other refs to push, Git uses (in order of precedence):
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]. OPTIONS
Not all updates are allowed: see PUSH RULES below for the details.
GIT URLSIn general, URLs contain information about the transport protocol, the address of the remote server, and the path to the repository. Depending on the transport protocol, some of this information may be absent. Git supports ssh, git, http, and https protocols (in addition, ftp and ftps can be used for fetching, but this is inefficient and deprecated; do not use them). The native transport (i.e. The following syntaxes may be used with them:
An alternative scp-like syntax may also be used with the ssh protocol:
This syntax is only recognized if there are no slashes before the
first colon. This helps differentiate a local path that contains a
colon. For example the local path The ssh and git protocols additionally support
For local repositories, also supported by Git natively, the following syntaxes may be used:
These two syntaxes are mostly equivalent, except when cloning, when
the former implies
When Git doesn’t know how to handle a certain transport protocol, it
attempts to use the
where <address> may be a path, a server and path, or an arbitrary URL-like string recognized by the specific remote helper being invoked. See gitremote-helpers[7] for details. If there are a large number of similarly-named remote repositories and you want to use a different format for them (such that the URLs you use will be rewritten into URLs that work), you can create a configuration section of the form: [url "<actual-url-base>"] insteadOf = <other-url-base> For example, with this: [url "git://git.host.xz/"] insteadOf = host.xz:/path/to/ insteadOf = work: a URL like "work:repo.git" or like "host.xz:/path/to/repo.git" will be rewritten in any context that takes a URL to be "git://git.host.xz/repo.git". If you want to rewrite URLs for push only, you can create a configuration section of the form: [url "<actual-url-base>"] pushInsteadOf = <other-url-base> For example, with this: [url "ssh://example.org/"] pushInsteadOf = git://example.org/ a URL like "git://example.org/path/to/repo.git" will be rewritten to "ssh://example.org/path/to/repo.git" for pushes, but pulls will still use the original URL. REMOTESThe name of one of the following can be used instead of a URL as <repository> argument:
All of these also allow you to omit the refspec from the command line because they each contain a refspec which git will use by default. Named remote in configuration fileYou can choose to provide the name of a remote which you had previously
configured using git-remote[1], git-config[1]
or even by a manual edit to the [remote "<name>"] url = <URL> pushurl = <pushurl> push = <refspec> fetch = <refspec> The <pushurl> is used for pushes only. It is optional and defaults to <URL>. Pushing to a remote affects all defined pushurls or all defined urls if no pushurls are defined. Fetch, however, will only fetch from the first defined url if multiple urls are defined. Named file in
|
|
Note
|
Upstream branches are sometimes referred to as "tracking information", as in "set the branch’s tracking information". |
REMOTE GROUPS
A remote group is a named list of remotes configured via remotes.<name>
in your git config:
$ git config remotes.all-remotes "r1 r2 r3"
When a group name is given as the <repository> argument, the push is performed to each member remote in turn. The defining principle is:
git push <options> all-remotes <args>
is exactly equivalent to:
git push <options> r1 <args> git push <options> r2 <args> ... git push <options> rN <args>
where r1, r2, …, rN are the members of all-remotes. No special
behaviour is added or removed — the group is purely a shorthand for
running the same push command against each member remote individually.
When pushing to a group of more than one remote, Git spawns a separate
git push subprocess for each member remote in sequence. Each subprocess
receives the same flags and refspecs as the original invocation. This
means that per-remote push mappings configured via remote.<name>.push
and mirror mode (remote.<name>.mirror) are evaluated independently for
each remote, and a mirror remote in the group cannot affect the push
behaviour of other non-mirror remotes in the same group.
The --atomic option is not supported for group pushes, because atomicity
can only be guaranteed within a single transport connection to a single
remote. Git will refuse the invocation with an error if --atomic is
combined with a group name.
If any member remote fails whether due to a push rejection (e.g. a non-fast-forward update, a server-side hook refusing a ref) or a connection error (e.g. the repository does not exist, authentication fails, or the network is unreachable), Git reports the error and continues pushing to the remaining remotes in the group. The overall exit code is non-zero if any member push fails.
This means the user is responsible for ensuring that the sequence of
individual pushes makes sense. If git push r1 would fail for a given
set of options and arguments, then git push all-remotes will fail in
the same way when it reaches r1. The group push does not do anything
special to make a failing individual push succeed.
OUTPUT
The output of "git push" depends on the transport method used; this section describes the output when pushing over the Git protocol (either locally or via ssh).
The status of the push is output in tabular form, with each line representing the status of a single ref. Each line is of the form:
<flag> <summary> <from> -> <to> (<reason>)
If --porcelain is used, then each line of the output is of the form:
<flag> \t <from>:<to> \t <summary> (<reason>)
The status of up-to-date refs is shown only if --porcelain or --verbose
option is used.
- <flag>
-
A single character indicating the status of the ref:
- <summary>
-
For a successfully pushed ref, the summary shows the old and new values of the ref in a form suitable for using as an argument to
gitlog(this is <old>..<new> in most cases, and <old>...<new> for forced non-fast-forward updates).For a failed update, more details are given:
- rejected
-
Git did not try to send the ref at all, typically because it is not a fast-forward and you did not force the update.
- remote rejected
-
The remote end refused the update. Usually caused by a hook on the remote side, or because the remote repository has one of the following safety options in effect:
receive.denyCurrentBranch(for pushes to the checked out branch),receive.denyNonFastForwards(for forced non-fast-forward updates),receive.denyDeletesorreceive.denyDeleteCurrent. See git-config[1]. - remote failure
-
The remote end did not report the successful update of the ref, perhaps because of a temporary error on the remote side, a break in the network connection, or other transient error.
- from
-
The name of the local ref being pushed, minus its
refs/<type>/prefix. In the case of deletion, the name of the local ref is omitted. - to
-
The name of the remote ref being updated, minus its
refs/<type>/prefix. - reason
-
A human-readable explanation. In the case of successfully pushed refs, no explanation is needed. For a failed ref, the reason for failure is described.
PUSH RULES
As a safety feature, the git push command only allows certain kinds of
updates to prevent you from accidentally losing data on the remote.
Because branches and tags are intended to be used differently, the safety rules for pushing to a branch are different from the rules for pushing to a tag. In the following rules "update" means any modifications except deletions and creations. Deletions and creations are always allowed, except when forbidden by configuration or hooks.
-
If the push destination is a branch (
refs/heads/*): only fast-forward updates are allowed, which means the destination must be an ancestor of the source commit. The source must be a commit. -
If the push destination is a tag (
refs/tags/*): all updates will be rejected. The source can be any object. -
If the push destination is not a branch or tag:
-
If the source is a tree or blob object, any updates will be rejected
-
If the source is a tag or commit object, any fast-forward update is allowed, even in cases where what’s being fast-forwarded is not a commit, but a tag object which happens to point to a new commit which is a fast-forward of the commit the last tag (or commit) it’s replacing. Replacing a tag with an entirely different tag is also allowed, if it points to the same commit, as well as pushing a peeled tag, i.e. pushing the commit that existing tag object points to, or a new tag object which an existing commit points to.
-
You can override these rules by passing --force or by adding the
optional leading + to a refspec. The only exceptions are that no
amount of forcing will make a branch accept a non-commit object,
and forcing won’t make the remote repository accept a push that it’s
configured to deny.
Hooks and configuration can also override or amend these rules,
see e.g. receive.denyNonFastForwards and receive.denyDeletes
in git-config[1] and pre-receive and update in
githooks[5].
NOTE ABOUT FAST-FORWARDS
When an update changes a branch (or more in general, a ref) that used to point at commit A to point at another commit B, it is called a fast-forward update if and only if B is a descendant of A.
In a fast-forward update from A to B, the set of commits that the original commit A built on top of is a subset of the commits the new commit B builds on top of. Hence, it does not lose any history.
In contrast, a non-fast-forward update will lose history. For example, suppose you and somebody else started at the same commit X, and you built a history leading to commit B while the other person built a history leading to commit A. The history looks like this:
B
/
---X---A
Further suppose that the other person already pushed changes leading to A back to the original repository from which you two obtained the original commit X.
The push done by the other person updated the branch that used to point at commit X to point at commit A. It is a fast-forward.
But if you try to push, you will attempt to update the branch (that now points at A) with commit B. This does not fast-forward. If you did so, the changes introduced by commit A will be lost, because everybody will now start building on top of B.
The command by default does not allow an update that is not a fast-forward to prevent such loss of history.
If you do not want to lose your work (history from X to B) or the work by the other person (history from X to A), you would need to first fetch the history from the repository, create a history that contains changes done by both parties, and push the result back.
You can perform "git pull", resolve potential conflicts, and "git push" the result. A "git pull" will create a merge commit C between commits A and B.
B---C
/ /
---X---A
Updating A with the resulting merge commit will fast-forward and your push will be accepted.
Alternatively, you can rebase your change between X and B on top of A,
with git pull --rebase, and push the result back. The rebase will
create a new commit D that builds the change between X and B on top of
A.
B D
/ /
---X---A
Again, updating A with this commit will fast-forward and your push will be accepted.
There is another common situation where you may encounter non-fast-forward
rejection when you try to push, and it is possible even when you are
pushing into a repository nobody else pushes into. After you push commit
A yourself (in the first picture in this section), replace it with git
commit --amend to produce commit B, and you try to push it out, because
forgot that you have pushed A out already. In such a case, and only if
you are certain that nobody in the meantime fetched your earlier commit A
(and started building on top of it), you can run git push --force to
overwrite it. In other words, git push --force is a method reserved for
a case where you do mean to lose history.
EXAMPLES
gitpush-
Works like
gitpush<remote>, where <remote> is the current branch’s remote (ororigin, if no remote is configured for the current branch). gitpushorigin-
Without additional configuration, pushes the current branch to the configured upstream (
branch.<name>.mergeconfiguration variable) if it has the same name as the current branch, and errors out without pushing otherwise.The default behavior of this command when no <refspec> is given can be configured by setting the
pushoption of the remote, or thepush.defaultconfiguration variable.For example, to default to pushing only the current branch to
originusegitconfigremote.origin.pushHEAD. Any valid <refspec> (like the ones in the examples below) can be configured as the default forgitpushorigin. gitpushorigin:-
Push "matching" branches to
origin. See <refspec> in the OPTIONS section above for a description of "matching" branches. gitpushoriginmaster-
Find a ref that matches
masterin the source repository (most likely, it would findrefs/heads/master), and update the same ref (e.g.refs/heads/master) inoriginrepository with it. Ifmasterdid not exist remotely, it would be created. gitpushoriginHEAD-
A handy way to push the current branch to the same name on the remote.
gitpushmothershipmaster:satellite/masterdev:satellite/dev-
Use the source ref that matches
master(e.g.refs/heads/master) to update the ref that matchessatellite/master(most probablyrefs/remotes/satellite/master) in themothershiprepository; do the same fordevandsatellite/dev.See the section describing <refspec>... above for a discussion of the matching semantics.
This is to emulate
gitfetchrun on themothershipusinggitpushthat is run in the opposite direction in order to integrate the work done onsatellite, and is often necessary when you can only make connection in one way (i.e. satellite can ssh into mothership but mothership cannot initiate connection to satellite because the latter is behind a firewall or does not run sshd).After running this
gitpushon thesatellitemachine, you would ssh into themothershipand rungitmergethere to complete the emulation ofgitpullthat were run onmothershipto pull changes made onsatellite. gitpushoriginHEAD:master-
Push the current branch to the remote ref matching
masterin theoriginrepository. This form is convenient to push the current branch without thinking about its local name. gitpushoriginmaster:refs/heads/experimental-
Create the branch
experimentalin theoriginrepository by copying the currentmasterbranch. This form is only needed to create a new branch or tag in the remote repository when the local name and the remote name are different; otherwise, the ref name on its own will work. gitpushorigin:experimental-
Find a ref that matches
experimentalin theoriginrepository (e.g.refs/heads/experimental), and delete it. gitpushorigin+dev:master-
Update the origin repository’s master branch with the dev branch, allowing non-fast-forward updates. This can leave unreferenced commits dangling in the origin repository. Consider the following situation, where a fast-forward is not possible:
o---o---o---A---B origin/master \ X---Y---Z dev
The above command would change the origin repository to
A---B (unnamed branch) / o---o---o---X---Y---Z master
Commits A and B would no longer belong to a branch with a symbolic name, and so would be unreachable. As such, these commits would be removed by a
gitgccommand on the origin repository.
SECURITY
The fetch and push protocols are not designed to prevent one side from stealing data from the other repository that was not intended to be shared. If you have private data that you need to protect from a malicious peer, your best option is to store it in another repository. This applies to both clients and servers. In particular, namespaces on a server are not effective for read access control; you should only grant read access to a namespace to clients that you would trust with read access to the entire repository.
The known attack vectors are as follows:
-
The victim sends "have" lines advertising the IDs of objects it has that are not explicitly intended to be shared but can be used to optimize the transfer if the peer also has them. The attacker chooses an object ID X to steal and sends a ref to X, but isn’t required to send the content of X because the victim already has it. Now the victim believes that the attacker has X, and it sends the content of X back to the attacker later. (This attack is most straightforward for a client to perform on a server, by creating a ref to X in the namespace the client has access to and then fetching it. The most likely way for a server to perform it on a client is to "merge" X into a public branch and hope that the user does additional work on this branch and pushes it back to the server without noticing the merge.)
-
As in #1, the attacker chooses an object ID X to steal. The victim sends an object Y that the attacker already has, and the attacker falsely claims to have X and not Y, so the victim sends Y as a delta against X. The delta reveals regions of X that are similar to Y to the attacker.
CONFIGURATION
Everything below this line in this section is selectively included from the git-config[1] documentation. The content is the same as what’s found there:
push.autoSetupRemote-
If set to
trueassume--set-upstreamon default push when no upstream tracking exists for the current branch; this option takes effect withpush.defaultoptionssimple,upstream, andcurrent. It is useful if by default you want new branches to be pushed to the default remote (like the behavior ofpush.default=current) and you also want the upstream tracking to be set. Workflows most likely to benefit from this option aresimplecentral workflows where all branches are expected to have the same name on the remote. push.default-
Defines the action
gitpushshould take if no refspec is given (whether from the command-line, config, or elsewhere). Different values are well-suited for specific workflows; for instance, in a purely central workflow (i.e. the fetch source is equal to the push destination),upstreamis probably what you want. Possible values are:nothing-
do not push anything (error out) unless a refspec is given. This is primarily meant for people who want to avoid mistakes by always being explicit.
current-
push the current branch to update a branch with the same name on the receiving end. Works in both central and non-central workflows.
upstream-
push the current branch back to the branch whose changes are usually integrated into the current branch (which is called
@{upstream}). This mode only makes sense if you are pushing to the same repository you would normally pull from (i.e. central workflow). tracking-
this is a deprecated synonym for
upstream. simple-
push the current branch with the same name on the remote.
This mode requires that the remote repository to be pushed to is known. When pushing back to the same remote you pull from, the current branch must also have an upstream tracking branch with the same name.
This mode is the default since Git 2.0, and is the safest option suited for beginners.
matching-
push all branches having the same name on both ends. This makes the repository you are pushing to remember the set of branches that will be pushed out (e.g. if you always push
maintandmasterthere and no other branches, the repository you push to will have these two branches, and your localmaintandmasterwill be pushed there).To use this mode effectively, you have to make sure all the branches you would push out are ready to be pushed out before running
gitpush, as the whole point of this mode is to allow you to push all of the branches in one go. If you usually finish work on only one branch and push out the result, while other branches are unfinished, this mode is not for you. Also this mode is not suitable for pushing into a shared central repository, as other people may add new branches there, or update the tip of existing branches outside your control.This used to be the default, but not since Git 2.0 (
simpleis the new default).
push.followTags-
If set to true, enable
--follow-tagsoption by default. You may override this configuration at time of push by specifying--no-follow-tags. push.gpgSign-
May be set to a boolean value, or the string
if-asked. A true value causes all pushes to be GPG signed, as if--signedis passed to git-push[1]. The stringif-askedcauses pushes to be signed if the server supports it, as if--signed=if-askedis passed togitpush. A false value may override a value from a lower-priority config file. An explicit command-line flag always overrides this config option. push.pushOption-
When no
--push-option=<option> argument is given from the command line,gitpushbehaves as if each <option> of this variable is given as--push-option=<option>.This is a multi-valued variable, and an empty value can be used in a higher priority configuration file (e.g.
.git/configin a repository) to clear the values inherited from a lower priority configuration files (e.g.$HOME/.gitconfig).Example: /etc/gitconfig push.pushoption = a push.pushoption = b ~/.gitconfig push.pushoption = c repo/.git/config push.pushoption = push.pushoption = b This will result in only b (a and c are cleared).
push.recurseSubmodules-
May be
check,on-demand,only, orno, with the same behavior as that ofpush--recurse-submodules. If not set,nois used by default, unlesssubmodule.recurseis set (in which case atruevalue meanson-demand). push.useForceIfIncludes-
If set to
true, it is equivalent to specifying--force-if-includesas an option to git-push[1] in the command line. Adding--no-force-if-includesat the time of push overrides this configuration setting. push.negotiate-
If set to
true, attempt to reduce the size of the packfile sent by rounds of negotiation in which the client and the server attempt to find commits in common. Iffalse, Git will rely solely on the server’s ref advertisement to find commits in common. push.useBitmaps-
If set to
false, disable use of bitmaps forgitpusheven ifpack.useBitmapsistrue, without preventing other git operations from using bitmaps. Default istrue.
GIT
Part of the git[1] suite
push
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.