6 git-push - Update remote refs along with associated objects
12 'git push' [--all | --mirror | --tags] [-n | --dry-run] [--receive-pack=<git-receive-pack>]
13 [--repo=<repository>] [-f | --force] [-v | --verbose] [-u | --set-upstream]
14 [<repository> <refspec>...]
19 Updates remote refs using local refs, while sending objects
20 necessary to complete the given refs.
22 You can make interesting things happen to a repository
23 every time you push into it, by setting up 'hooks' there. See
24 documentation for linkgit:git-receive-pack[1].
30 The "remote" repository that is destination of a push
31 operation. This parameter can be either a URL
32 (see the section <<URLS,GIT URLS>> below) or the name
33 of a remote (see the section <<REMOTES,REMOTES>> below).
36 The format of a <refspec> parameter is an optional plus
37 `{plus}`, followed by the source ref <src>, followed
38 by a colon `:`, followed by the destination ref <dst>.
39 It is used to specify with what <src> object the <dst> ref
40 in the remote repository is to be updated.
42 The <src> is often the name of the branch you would want to push, but
43 it can be any arbitrary "SHA-1 expression", such as `master~4` or
44 `HEAD` (see linkgit:git-rev-parse[1]).
46 The <dst> tells which ref on the remote side is updated with this
47 push. Arbitrary expressions cannot be used here, an actual ref must
48 be named. If `:`<dst> is omitted, the same ref as <src> will be
51 The object referenced by <src> is used to update the <dst> reference
52 on the remote side, but by default this is only allowed if the
53 update can fast-forward <dst>. By having the optional leading `{plus}`,
54 you can tell git to update the <dst> ref even when the update is not a
55 fast-forward. This does *not* attempt to merge <src> into <dst>. See
56 EXAMPLES below for details.
58 `tag <tag>` means the same as `refs/tags/<tag>:refs/tags/<tag>`.
60 Pushing an empty <src> allows you to delete the <dst> ref from
61 the remote repository.
63 The special refspec `:` (or `{plus}:` to allow non-fast-forward updates)
64 directs git to push "matching" branches: for every branch that exists on
65 the local side, the remote side is updated if a branch of the same name
66 already exists on the remote side. This is the default operation mode
67 if no explicit refspec is found (that is neither on the command line
68 nor in any Push line of the corresponding remotes file---see below).
71 Instead of naming each ref to push, specifies that all
72 refs under `$GIT_DIR/refs/heads/` be pushed.
75 Instead of naming each ref to push, specifies that all
76 refs under `$GIT_DIR/refs/` (which includes but is not
77 limited to `refs/heads/`, `refs/remotes/`, and `refs/tags/`)
78 be mirrored to the remote repository. Newly created local
79 refs will be pushed to the remote end, locally updated refs
80 will be force updated on the remote end, and deleted refs
81 will be removed from the remote end. This is the default
82 if the configuration option `remote.<remote>.mirror` is
87 Do everything except actually send the updates.
90 Produce machine-readable output. The output status line for each ref
91 will be tab-separated and sent to stdout instead of stderr. The full
92 symbolic names of the refs will be given.
95 All listed refs are deleted from the remote repository. This is
96 the same as prefixing all refs with a colon.
99 All refs under `$GIT_DIR/refs/tags` are pushed, in
100 addition to refspecs explicitly listed on the command
103 --receive-pack=<git-receive-pack>::
104 --exec=<git-receive-pack>::
105 Path to the 'git-receive-pack' program on the remote
106 end. Sometimes useful when pushing to a remote
107 repository over ssh, and you do not have the program in
108 a directory on the default $PATH.
112 Usually, the command refuses to update a remote ref that is
113 not an ancestor of the local ref used to overwrite it.
114 This flag disables the check. This can cause the
115 remote repository to lose commits; use it with care.
117 --repo=<repository>::
118 This option is only relevant if no <repository> argument is
119 passed in the invocation. In this case, 'git push' derives the
120 remote name from the current branch: If it tracks a remote
121 branch, then that remote repository is pushed to. Otherwise,
122 the name "origin" is used. For this latter case, this option
123 can be used to override the name "origin". In other words,
124 the difference between these two commands
126 --------------------------
128 git push --repo=public #2
129 --------------------------
131 is that #1 always pushes to "public" whereas #2 pushes to "public"
132 only if the current branch does not track a remote branch. This is
133 useful if you write an alias or script around 'git push'.
137 For every branch that is up to date or successfully pushed, add
138 upstream (tracking) reference, used by argument-less
139 linkgit:git-pull[1] and other commands. For more information,
140 see 'branch.<name>.merge' in linkgit:git-config[1].
144 These options are passed to 'git send-pack'. Thin
145 transfer spends extra cycles to minimize the number of
146 objects to be sent and meant to be used on slower connection.
150 Suppress all output, including the listing of updated refs,
151 unless an error occurs. Progress is not reported to the standard
159 Progress status is reported on the standard error stream
160 by default when it is attached to a terminal, unless -q
161 is specified. This flag forces progress status even if the
162 standard error stream is not directed to a terminal.
164 include::urls-remotes.txt[]
169 The output of "git push" depends on the transport method used; this
170 section describes the output when pushing over the git protocol (either
173 The status of the push is output in tabular form, with each line
174 representing the status of a single ref. Each line is of the form:
176 -------------------------------
177 <flag> <summary> <from> -> <to> (<reason>)
178 -------------------------------
180 If --porcelain is used, then each line of the output is of the form:
182 -------------------------------
183 <flag> \t <from>:<to> \t <summary> (<reason>)
184 -------------------------------
186 The status of up-to-date refs is shown only if --porcelain or --verbose
190 A single character indicating the status of the ref:
191 (space);; for a successfully pushed fast-forward;
192 `{plus}`;; for a successful forced update;
193 `-`;; for a successfully deleted ref;
194 `*`;; for a successfully pushed new ref;
195 `!`;; for a ref that was rejected or failed to push; and
196 `=`;; for a ref that was up to date and did not need pushing.
199 For a successfully pushed ref, the summary shows the old and new
200 values of the ref in a form suitable for using as an argument to
201 `git log` (this is `<old>..<new>` in most cases, and
202 `<old>...<new>` for forced non-fast-forward updates). For a
203 failed update, more details are given for the failure.
204 The string `rejected` indicates that git did not try to send the
205 ref at all (typically because it is not a fast-forward). The
206 string `remote rejected` indicates that the remote end refused
207 the update; this rejection is typically caused by a hook on the
208 remote side. The string `remote failure` indicates that the
209 remote end did not report the successful update of the ref
210 (perhaps because of a temporary error on the remote side, a
211 break in the network connection, or other transient error).
214 The name of the local ref being pushed, minus its
215 `refs/<type>/` prefix. In the case of deletion, the
216 name of the local ref is omitted.
219 The name of the remote ref being updated, minus its
220 `refs/<type>/` prefix.
223 A human-readable explanation. In the case of successfully pushed
224 refs, no explanation is needed. For a failed ref, the reason for
225 failure is described.
227 Note about fast-forwards
228 ------------------------
230 When an update changes a branch (or more in general, a ref) that used to
231 point at commit A to point at another commit B, it is called a
232 fast-forward update if and only if B is a descendant of A.
234 In a fast-forward update from A to B, the set of commits that the original
235 commit A built on top of is a subset of the commits the new commit B
236 builds on top of. Hence, it does not lose any history.
238 In contrast, a non-fast-forward update will lose history. For example,
239 suppose you and somebody else started at the same commit X, and you built
240 a history leading to commit B while the other person built a history
241 leading to commit A. The history looks like this:
251 Further suppose that the other person already pushed changes leading to A
252 back to the original repository you two obtained the original commit X.
254 The push done by the other person updated the branch that used to point at
255 commit X to point at commit A. It is a fast-forward.
257 But if you try to push, you will attempt to update the branch (that
258 now points at A) with commit B. This does _not_ fast-forward. If you did
259 so, the changes introduced by commit A will be lost, because everybody
260 will now start building on top of B.
262 The command by default does not allow an update that is not a fast-forward
263 to prevent such loss of history.
265 If you do not want to lose your work (history from X to B) nor the work by
266 the other person (history from X to A), you would need to first fetch the
267 history from the repository, create a history that contains changes done
268 by both parties, and push the result back.
270 You can perform "git pull", resolve potential conflicts, and "git push"
271 the result. A "git pull" will create a merge commit C between commits A
282 Updating A with the resulting merge commit will fast-forward and your
283 push will be accepted.
285 Alternatively, you can rebase your change between X and B on top of A,
286 with "git pull --rebase", and push the result back. The rebase will
287 create a new commit D that builds the change between X and B on top of
298 Again, updating A with this commit will fast-forward and your push will be
301 There is another common situation where you may encounter non-fast-forward
302 rejection when you try to push, and it is possible even when you are
303 pushing into a repository nobody else pushes into. After you push commit
304 A yourself (in the first picture in this section), replace it with "git
305 commit --amend" to produce commit B, and you try to push it out, because
306 forgot that you have pushed A out already. In such a case, and only if
307 you are certain that nobody in the meantime fetched your earlier commit A
308 (and started building on top of it), you can run "git push --force" to
309 overwrite it. In other words, "git push --force" is a method reserved for
310 a case where you do mean to lose history.
317 Works like `git push <remote>`, where <remote> is the
318 current branch's remote (or `origin`, if no remote is
319 configured for the current branch).
322 Without additional configuration, works like
325 The default behavior of this command when no <refspec> is given can be
326 configured by setting the `push` option of the remote.
328 For example, to default to pushing only the current branch to `origin`
329 use `git config remote.origin.push HEAD`. Any valid <refspec> (like
330 the ones in the examples below) can be configured as the default for
334 Push "matching" branches to `origin`. See
335 <refspec> in the <<OPTIONS,OPTIONS>> section above for a
336 description of "matching" branches.
338 git push origin master::
339 Find a ref that matches `master` in the source repository
340 (most likely, it would find `refs/heads/master`), and update
341 the same ref (e.g. `refs/heads/master`) in `origin` repository
342 with it. If `master` did not exist remotely, it would be
345 git push origin HEAD::
346 A handy way to push the current branch to the same name on the
349 git push origin master:satellite/master dev:satellite/dev::
350 Use the source ref that matches `master` (e.g. `refs/heads/master`)
351 to update the ref that matches `satellite/master` (most probably
352 `refs/remotes/satellite/master`) in the `origin` repository, then
353 do the same for `dev` and `satellite/dev`.
355 git push origin HEAD:master::
356 Push the current branch to the remote ref matching `master` in the
357 `origin` repository. This form is convenient to push the current
358 branch without thinking about its local name.
360 git push origin master:refs/heads/experimental::
361 Create the branch `experimental` in the `origin` repository
362 by copying the current `master` branch. This form is only
363 needed to create a new branch or tag in the remote repository when
364 the local name and the remote name are different; otherwise,
365 the ref name on its own will work.
367 git push origin :experimental::
368 Find a ref that matches `experimental` in the `origin` repository
369 (e.g. `refs/heads/experimental`), and delete it.
371 git push origin {plus}dev:master::
372 Update the origin repository's master branch with the dev branch,
373 allowing non-fast-forward updates. *This can leave unreferenced
374 commits dangling in the origin repository.* Consider the
375 following situation, where a fast-forward is not possible:
378 o---o---o---A---B origin/master
383 The above command would change the origin repository to
386 A---B (unnamed branch)
388 o---o---o---X---Y---Z master
391 Commits A and B would no longer belong to a branch with a symbolic name,
392 and so would be unreachable. As such, these commits would be removed by
393 a `git gc` command on the origin repository.
398 Written by Junio C Hamano <gitster@pobox.com>, later rewritten in C
399 by Linus Torvalds <torvalds@osdl.org>
403 Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>.
407 Part of the linkgit:git[1] suite