git rm: refresh index before up-to-date check
[git/git.git] / Documentation / git-push.txt
CommitLineData
215a7ad1
JH
1git-push(1)
2===========
7fc9d69f
JH
3
4NAME
5----
7bd7f280 6git-push - Update remote refs along with associated objects
7fc9d69f
JH
7
8
9SYNOPSIS
10--------
97925fde 11[verse]
b1889c36 12'git push' [--all] [--dry-run] [--tags] [--receive-pack=<git-receive-pack>]
2c9693bd
AMS
13 [--repo=all] [-f | --force] [-v | --verbose]
14 [<repository> <refspec>...]
7fc9d69f
JH
15
16DESCRIPTION
17-----------
ab9b3138
JH
18
19Updates remote refs using local refs, while sending objects
20necessary to complete the given refs.
7fc9d69f 21
cc55aaec 22You can make interesting things happen to a repository
eb0362a4 23every time you push into it, by setting up 'hooks' there. See
5162e697 24documentation for linkgit:git-receive-pack[1].
eb0362a4 25
7fc9d69f
JH
26
27OPTIONS
28-------
3598a308 29<repository>::
85a97d4e
BF
30 The "remote" repository that is destination of a push
31 operation. See the section <<URLS,GIT URLS>> below.
3598a308 32
2c9693bd 33<refspec>...::
3598a308 34 The canonical format of a <refspec> parameter is
0f4f4d15 35 `+?<src>:<dst>`; that is, an optional plus `{plus}`, followed
3598a308
BF
36 by the source ref, followed by a colon `:`, followed by
37 the destination ref.
38+
491b1b11
SV
39The <src> side represents the source branch (or arbitrary
40"SHA1 expression", such as `master~4` (four parents before the
41tip of `master` branch); see linkgit:git-rev-parse[1]) that you
42want to push. The <dst> side represents the destination location.
3598a308
BF
43+
44The local ref that matches <src> is used
491b1b11
SV
45to fast forward the remote ref that matches <dst> (or, if no <dst> was
46specified, the same ref that <src> referred to locally). If
47the optional leading plus `+` is used, the remote ref is updated
3598a308
BF
48even if it does not result in a fast forward update.
49+
25fb6290 50`tag <tag>` means the same as `refs/tags/<tag>:refs/tags/<tag>`.
3598a308 51+
bb9fca80
JH
52A parameter <ref> without a colon pushes the <ref> from the source
53repository to the destination repository under the same name.
25fb6290
JH
54+
55Pushing an empty <src> allows you to delete the <dst> ref from
56the remote repository.
a83619d6
PB
57+
58The special refspec `:` (or `+:` to allow non-fast forward updates)
59directs git to push "matching" heads: for every head that exists on
60the local side, the remote side is updated if a head of the same name
61already exists on the remote side. This is the default operation mode
62if no explicit refspec is found (that is neither on the command line
63nor in any Push line of the corresponding remotes file---see below).
7fc9d69f 64
3240240f 65--all::
cc55aaec 66 Instead of naming each ref to push, specifies that all
5c633a4c 67 refs under `$GIT_DIR/refs/heads/` be pushed.
d6a73596 68
3240240f 69--mirror::
ff206748 70 Instead of naming each ref to push, specifies that all
73f03627
SP
71 refs under `$GIT_DIR/refs/` (which includes but is not
72 limited to `refs/heads/`, `refs/remotes/`, and `refs/tags/`)
ff206748
AW
73 be mirrored to the remote repository. Newly created local
74 refs will be pushed to the remote end, locally updated refs
75 will be force updated on the remote end, and deleted refs
84bb2dfd
PB
76 will be removed from the remote end. This is the default
77 if the configuration option `remote.<remote>.mirror` is
78 set.
ff206748 79
3240240f 80--dry-run::
11f2441f
BE
81 Do everything except actually send the updates.
82
3240240f 83--tags::
42301e34
JH
84 All refs under `$GIT_DIR/refs/tags` are pushed, in
85 addition to refspecs explicitly listed on the command
86 line.
87
3240240f 88--receive-pack=<git-receive-pack>::
ba020ef5 89 Path to the 'git-receive-pack' program on the remote
5214f770
UKK
90 end. Sometimes useful when pushing to a remote
91 repository over ssh, and you do not have the program in
92 a directory on the default $PATH.
93
3240240f 94--exec=<git-receive-pack>::
d23842fd
UKK
95 Same as \--receive-pack=<git-receive-pack>.
96
3240240f
SB
97-f::
98--force::
f0fff36e 99 Usually, the command refuses to update a remote ref that is
64a476e6 100 not an ancestor of the local ref used to overwrite it.
f0fff36e
BF
101 This flag disables the check. This can cause the
102 remote repository to lose commits; use it with care.
7fc9d69f 103
3240240f 104--repo=<repo>::
dc36f265
JH
105 When no repository is specified the command defaults to
106 "origin"; this overrides it.
107
3240240f
SB
108--thin::
109--no-thin::
ba020ef5 110 These options are passed to 'git-send-pack'. Thin
dc36f265
JH
111 transfer spends extra cycles to minimize the number of
112 objects to be sent and meant to be used on slower connection.
113
3240240f
SB
114-v::
115--verbose::
dc36f265
JH
116 Run verbosely.
117
37ba0561 118include::urls-remotes.txt[]
eb0362a4 119
066a5268
JK
120OUTPUT
121------
122
123The output of "git push" depends on the transport method used; this
124section describes the output when pushing over the git protocol (either
125locally or via ssh).
126
127The status of the push is output in tabular form, with each line
128representing the status of a single ref. Each line is of the form:
129
130-------------------------------
131 <flag> <summary> <from> -> <to> (<reason>)
132-------------------------------
133
134flag::
135 A single character indicating the status of the ref. This is
136 blank for a successfully pushed ref, `!` for a ref that was
137 rejected or failed to push, and '=' for a ref that was up to
138 date and did not need pushing (note that the status of up to
139 date refs is shown only when `git push` is running verbosely).
140
141summary::
142 For a successfully pushed ref, the summary shows the old and new
143 values of the ref in a form suitable for using as an argument to
144 `git log` (this is `<old>..<new>` in most cases, and
145 `<old>...<new>` for forced non-fast forward updates). For a
146 failed update, more details are given for the failure.
147 The string `rejected` indicates that git did not try to send the
148 ref at all (typically because it is not a fast forward). The
149 string `remote rejected` indicates that the remote end refused
150 the update; this rejection is typically caused by a hook on the
151 remote side. The string `remote failure` indicates that the
152 remote end did not report the successful update of the ref
153 (perhaps because of a temporary error on the remote side, a
154 break in the network connection, or other transient error).
155
156from::
157 The name of the local ref being pushed, minus its
158 `refs/<type>/` prefix. In the case of deletion, the
159 name of the local ref is omitted.
160
161to::
162 The name of the remote ref being updated, minus its
163 `refs/<type>/` prefix.
164
165reason::
166 A human-readable explanation. In the case of successfully pushed
167 refs, no explanation is needed. For a failed ref, the reason for
168 failure is described.
bb9fca80
JH
169
170Examples
171--------
172
173git push origin master::
174 Find a ref that matches `master` in the source repository
175 (most likely, it would find `refs/heads/master`), and update
176 the same ref (e.g. `refs/heads/master`) in `origin` repository
491b1b11
SV
177 with it. If `master` did not exist remotely, it would be
178 created.
bb9fca80
JH
179
180git push origin :experimental::
181 Find a ref that matches `experimental` in the `origin` repository
182 (e.g. `refs/heads/experimental`), and delete it.
183
2c9693bd
AMS
184git push origin master:satellite/master dev:satellite/dev::
185 Use the source ref that matches `master` (e.g. `refs/heads/master`)
186 to update the ref that matches `satellite/master` (most probably
187 `refs/remotes/satellite/master`) in the `origin` repository, then
188 do the same for `dev` and `satellite/dev`.
bb9fca80 189
4e560158
SP
190git push origin master:refs/heads/experimental::
191 Create the branch `experimental` in the `origin` repository
491b1b11
SV
192 by copying the current `master` branch. This form is only
193 needed to create a new branch or tag in the remote repository when
194 the local name and the remote name are different; otherwise,
195 the ref name on its own will work.
4e560158 196
7fc9d69f
JH
197Author
198------
59eb68aa 199Written by Junio C Hamano <gitster@pobox.com>, later rewritten in C
25fb6290 200by Linus Torvalds <torvalds@osdl.org>
7fc9d69f
JH
201
202Documentation
203--------------
204Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>.
205
206GIT
207---
9e1f0a85 208Part of the linkgit:git[1] suite