Google Git
Sign in
chromium / external / gitster / git-htmldocs / 0e88f3e399da078c8e389db57ca99569c3fdd3a8 / . / git-push.html
blob: e27e34a3ba853e05c39c1be7cc57545b2e040b48 [file] [log] [blame]
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]1<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
2 "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
3<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
4<head>
5<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]6<meta name="generator" content="AsciiDoc 8.2.5" />
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]7<style type="text/css">
8/* Debug borders */
9p, li, dt, dd, div, pre, h1, h2, h3, h4, h5, h6 {
10/*
11 border: 1px solid red;
12*/
13}
14
15body {
16 margin: 1em 5% 1em 5%;
17}
18
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]19a {
20 color: blue;
21 text-decoration: underline;
22}
23a:visited {
24 color: fuchsia;
25}
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]26
27em {
28 font-style: italic;
29}
30
31strong {
32 font-weight: bold;
33}
34
35tt {
36 color: navy;
37}
38
39h1, h2, h3, h4, h5, h6 {
40 color: #527bbd;
41 font-family: sans-serif;
42 margin-top: 1.2em;
43 margin-bottom: 0.5em;
44 line-height: 1.3;
45}
46
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]47h1, h2, h3 {
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]48 border-bottom: 2px solid silver;
49}
50h2 {
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]51 padding-top: 0.5em;
52}
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]53h3 {
54 float: left;
55}
56h3 + * {
57 clear: left;
58}
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]59
60div.sectionbody {
61 font-family: serif;
62 margin-left: 0;
63}
64
65hr {
66 border: 1px solid silver;
67}
68
69p {
70 margin-top: 0.5em;
71 margin-bottom: 0.5em;
72}
73
74pre {
75 padding: 0;
76 margin: 0;
77}
78
79span#author {
80 color: #527bbd;
81 font-family: sans-serif;
82 font-weight: bold;
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]83 font-size: 1.1em;
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]84}
85span#email {
86}
87span#revision {
88 font-family: sans-serif;
89}
90
91div#footer {
92 font-family: sans-serif;
93 font-size: small;
94 border-top: 2px solid silver;
95 padding-top: 0.5em;
96 margin-top: 4.0em;
97}
98div#footer-text {
99 float: left;
100 padding-bottom: 0.5em;
101}
102div#footer-badges {
103 float: right;
104 padding-bottom: 0.5em;
105}
106
107div#preamble,
108div.tableblock, div.imageblock, div.exampleblock, div.verseblock,
109div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
110div.admonitionblock {
111 margin-right: 10%;
112 margin-top: 1.5em;
113 margin-bottom: 1.5em;
114}
115div.admonitionblock {
116 margin-top: 2.5em;
117 margin-bottom: 2.5em;
118}
119
120div.content { /* Block element content. */
121 padding: 0;
122}
123
124/* Block element titles. */
125div.title, caption.title {
126 font-family: sans-serif;
127 font-weight: bold;
128 text-align: left;
129 margin-top: 1.0em;
130 margin-bottom: 0.5em;
131}
132div.title + * {
133 margin-top: 0;
134}
135
136td div.title:first-child {
137 margin-top: 0.0em;
138}
139div.content div.title:first-child {
140 margin-top: 0.0em;
141}
142div.content + div.title {
143 margin-top: 0.0em;
144}
145
146div.sidebarblock > div.content {
147 background: #ffffee;
148 border: 1px solid silver;
149 padding: 0.5em;
150}
151
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]152div.listingblock {
153 margin-right: 0%;
154}
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]155div.listingblock > div.content {
156 border: 1px solid silver;
157 background: #f4f4f4;
158 padding: 0.5em;
159}
160
161div.quoteblock > div.content {
162 padding-left: 2.0em;
163}
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]164
165div.attribution {
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]166 text-align: right;
167}
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]168div.verseblock + div.attribution {
169 text-align: left;
170}
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]171
172div.admonitionblock .icon {
173 vertical-align: top;
174 font-size: 1.1em;
175 font-weight: bold;
176 text-decoration: underline;
177 color: #527bbd;
178 padding-right: 0.5em;
179}
180div.admonitionblock td.content {
181 padding-left: 0.5em;
182 border-left: 2px solid silver;
183}
184
185div.exampleblock > div.content {
186 border-left: 2px solid silver;
187 padding: 0.5em;
188}
189
190div.verseblock div.content {
191 white-space: pre;
192}
193
194div.imageblock div.content { padding-left: 0; }
195div.imageblock img { border: 1px solid silver; }
196span.image img { border-style: none; }
197
198dl {
199 margin-top: 0.8em;
200 margin-bottom: 0.8em;
201}
202dt {
203 margin-top: 0.5em;
204 margin-bottom: 0;
205 font-style: italic;
206}
207dd > *:first-child {
208 margin-top: 0;
209}
210
211ul, ol {
212 list-style-position: outside;
213}
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]214div.olist2 ol {
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]215 list-style-type: lower-alpha;
216}
217
218div.tableblock > table {
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]219 border: 3px solid #527bbd;
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]220}
221thead {
222 font-family: sans-serif;
223 font-weight: bold;
224}
225tfoot {
226 font-weight: bold;
227}
228
229div.hlist {
230 margin-top: 0.8em;
231 margin-bottom: 0.8em;
232}
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]233div.hlist td {
234 padding-bottom: 5px;
235}
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]236td.hlist1 {
237 vertical-align: top;
238 font-style: italic;
239 padding-right: 0.8em;
240}
241td.hlist2 {
242 vertical-align: top;
243}
244
245@media print {
246 div#footer-badges { display: none; }
247}
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]248
249div#toctitle {
250 color: #527bbd;
251 font-family: sans-serif;
252 font-size: 1.1em;
253 font-weight: bold;
254 margin-top: 1.0em;
255 margin-bottom: 0.1em;
256}
257
258div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
259 margin-top: 0;
260 margin-bottom: 0;
261}
262div.toclevel2 {
263 margin-left: 2em;
264 font-size: 0.9em;
265}
266div.toclevel3 {
267 margin-left: 4em;
268 font-size: 0.9em;
269}
270div.toclevel4 {
271 margin-left: 6em;
272 font-size: 0.9em;
273}
274include1::./stylesheets/xhtml11-manpage.css[]
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]275/* Workarounds for IE6's broken and incomplete CSS2. */
276
277div.sidebar-content {
278 background: #ffffee;
279 border: 1px solid silver;
280 padding: 0.5em;
281}
282div.sidebar-title, div.image-title {
283 font-family: sans-serif;
284 font-weight: bold;
285 margin-top: 0.0em;
286 margin-bottom: 0.5em;
287}
288
289div.listingblock div.content {
290 border: 1px solid silver;
291 background: #f4f4f4;
292 padding: 0.5em;
293}
294
295div.quoteblock-content {
296 padding-left: 2.0em;
297}
298
299div.exampleblock-content {
300 border-left: 2px solid silver;
301 padding-left: 0.5em;
302}
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]303
304/* IE6 sets dynamically generated links as visited. */
305div#toc a:visited { color: blue; }
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]306</style>
307<title>git-push(1)</title>
308</head>
309<body>
310<div id="header">
311<h1>
312git-push(1) Manual Page
313</h1>
314<h2>NAME</h2>
315<div class="sectionbody">
316<p>git-push -
Junio C Hamano01078922006-03-10 00:31:47[diff] [blame]317 Update remote refs along with associated objects
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]318</p>
319</div>
320</div>
321<h2>SYNOPSIS</h2>
322<div class="sectionbody">
Junio C Hamanoa9b8d242007-05-19 04:51:55[diff] [blame]323<div class="verseblock">
Junio C Hamano4007b5d2009-02-19 00:54:28[diff] [blame]324<div class="content"><em>git push</em> [--all | --mirror | --tags] [--dry-run] [--receive-pack=&lt;git-receive-pack&gt;]
Junio C Hamanoa476efa2008-10-10 15:31:42[diff] [blame]325 [--repo=&lt;repository&gt;] [-f | --force] [-v | --verbose]
Junio C Hamano7f80ae82008-07-30 18:31:35[diff] [blame]326 [&lt;repository&gt; &lt;refspec&gt;&#8230;]</div></div>
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]327</div>
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]328<h2 id="_description">DESCRIPTION</h2>
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]329<div class="sectionbody">
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]330<div class="para"><p>Updates remote refs using local refs, while sending objects
331necessary to complete the given refs.</p></div>
332<div class="para"><p>You can make interesting things happen to a repository
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]333every time you push into it, by setting up <em>hooks</em> there. See
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]334documentation for <a href="git-receive-pack.html">git-receive-pack(1)</a>.</p></div>
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]335</div>
Junio C Hamanoea82cff2009-03-18 01:54:48[diff] [blame]336<h2 id="_options_a_id_options_a">OPTIONS<a id="OPTIONS"></a></h2>
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]337<div class="sectionbody">
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]338<div class="vlist"><dl>
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]339<dt>
340&lt;repository&gt;
341</dt>
342<dd>
343<p>
Junio C Hamano40f2f8d2006-02-07 08:04:39[diff] [blame]344 The "remote" repository that is destination of a push
Junio C Hamanocc0cb312009-01-22 03:38:50[diff] [blame]345 operation. This parameter can be either a URL
346 (see the section <a href="#URLS">GIT URLS</a> below) or the name
347 of a remote (see the section <a href="#REMOTES">REMOTES</a> below).
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]348</p>
Junio C Hamano40f2f8d2006-02-07 08:04:39[diff] [blame]349</dd>
350<dt>
Junio C Hamano7f80ae82008-07-30 18:31:35[diff] [blame]351&lt;refspec&gt;&#8230;
Junio C Hamano40f2f8d2006-02-07 08:04:39[diff] [blame]352</dt>
353<dd>
354<p>
Junio C Hamano8b6e23b2009-02-01 06:36:08[diff] [blame]355 The format of a &lt;refspec&gt; parameter is an optional plus
356 <tt>&#43;</tt>, followed by the source ref &lt;src&gt;, followed
357 by a colon <tt>:</tt>, followed by the destination ref &lt;dst&gt;.
358 It is used to specify with what &lt;src&gt; object the &lt;dst&gt; ref
359 in the remote repository is to be updated.
Junio C Hamano40f2f8d2006-02-07 08:04:39[diff] [blame]360</p>
Junio C Hamano8b6e23b2009-02-01 06:36:08[diff] [blame]361<div class="para"><p>The &lt;src&gt; is often the name of the branch you would want to push, but
362it can be any arbitrary "SHA-1 expression", such as <tt>master~4</tt> or
363<tt>HEAD</tt> (see <a href="git-rev-parse.html">git-rev-parse(1)</a>).</p></div>
364<div class="para"><p>The &lt;dst&gt; tells which ref on the remote side is updated with this
365push. Arbitrary expressions cannot be used here, an actual ref must
366be named. If <tt>:</tt>&lt;dst&gt; is omitted, the same ref as &lt;src&gt; will be
367updated.</p></div>
Junio C Hamanod533bdb2009-02-25 09:56:58[diff] [blame]368<div class="para"><p>The object referenced by &lt;src&gt; is used to update the &lt;dst&gt; reference
369on the remote side, but by default this is only allowed if the
370update can fast forward &lt;dst&gt;. By having the optional leading <tt>&#43;</tt>,
371you can tell git to update the &lt;dst&gt; ref even when the update is not a
372fast forward. This does <strong>not</strong> attempt to merge &lt;src&gt; into &lt;dst&gt;. See
373EXAMPLES below for details.</p></div>
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]374<div class="para"><p><tt>tag &lt;tag&gt;</tt> means the same as <tt>refs/tags/&lt;tag&gt;:refs/tags/&lt;tag&gt;</tt>.</p></div>
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]375<div class="para"><p>Pushing an empty &lt;src&gt; allows you to delete the &lt;dst&gt; ref from
376the remote repository.</p></div>
Junio C Hamanod533bdb2009-02-25 09:56:58[diff] [blame]377<div class="para"><p>The special refspec <tt>:</tt> (or <tt>&#43;:</tt> to allow non-fast forward updates)
Junio C Hamanocc0cb312009-01-22 03:38:50[diff] [blame]378directs git to push "matching" branches: for every branch that exists on
379the local side, the remote side is updated if a branch of the same name
Junio C Hamanob713ff12008-05-24 01:12:30[diff] [blame]380already exists on the remote side. This is the default operation mode
381if no explicit refspec is found (that is neither on the command line
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]382nor in any Push line of the corresponding remotes file---see below).</p></div>
Junio C Hamano40f2f8d2006-02-07 08:04:39[diff] [blame]383</dd>
384<dt>
385--all
386</dt>
387<dd>
388<p>
389 Instead of naming each ref to push, specifies that all
Junio C Hamanod2d9ae12007-09-19 02:27:57[diff] [blame]390 refs under <tt>$GIT_DIR/refs/heads/</tt> be pushed.
Junio C Hamano40f2f8d2006-02-07 08:04:39[diff] [blame]391</p>
392</dd>
393<dt>
Junio C Hamano9d2bbb72007-11-25 04:56:07[diff] [blame]394--mirror
395</dt>
396<dd>
397<p>
398 Instead of naming each ref to push, specifies that all
Junio C Hamanoa351d142008-06-21 09:40:40[diff] [blame]399 refs under <tt>$GIT_DIR/refs/</tt> (which includes but is not
400 limited to <tt>refs/heads/</tt>, <tt>refs/remotes/</tt>, and <tt>refs/tags/</tt>)
Junio C Hamano9d2bbb72007-11-25 04:56:07[diff] [blame]401 be mirrored to the remote repository. Newly created local
402 refs will be pushed to the remote end, locally updated refs
403 will be force updated on the remote end, and deleted refs
Junio C Hamano47d68a52008-05-06 06:35:40[diff] [blame]404 will be removed from the remote end. This is the default
405 if the configuration option <tt>remote.&lt;remote&gt;.mirror</tt> is
406 set.
Junio C Hamano9d2bbb72007-11-25 04:56:07[diff] [blame]407</p>
408</dd>
409<dt>
Junio C Hamano764a6672007-10-23 01:23:31[diff] [blame]410--dry-run
411</dt>
412<dd>
413<p>
414 Do everything except actually send the updates.
415</p>
416</dd>
417<dt>
Junio C Hamano40f2f8d2006-02-07 08:04:39[diff] [blame]418--tags
419</dt>
420<dd>
421<p>
422 All refs under <tt>$GIT_DIR/refs/tags</tt> are pushed, in
423 addition to refspecs explicitly listed on the command
424 line.
425</p>
426</dd>
427<dt>
Junio C Hamano4ad294b2007-01-20 02:22:50[diff] [blame]428--receive-pack=&lt;git-receive-pack&gt;
Junio C Hamano1ce39ab2007-01-16 22:05:10[diff] [blame]429</dt>
Junio C Hamano1c958272009-01-12 18:04:21[diff] [blame]430<dt>
431--exec=&lt;git-receive-pack&gt;
432</dt>
Junio C Hamano1ce39ab2007-01-16 22:05:10[diff] [blame]433<dd>
434<p>
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]435 Path to the <em>git-receive-pack</em> program on the remote
Junio C Hamano1ce39ab2007-01-16 22:05:10[diff] [blame]436 end. Sometimes useful when pushing to a remote
437 repository over ssh, and you do not have the program in
438 a directory on the default $PATH.
439</p>
440</dd>
441<dt>
Junio C Hamanoeb415992008-06-08 22:49:47[diff] [blame]442-f
443</dt>
444<dt>
445--force
Junio C Hamano40f2f8d2006-02-07 08:04:39[diff] [blame]446</dt>
447<dd>
448<p>
449 Usually, the command refuses to update a remote ref that is
Junio C Hamano4cd1c0e2007-08-06 04:39:14[diff] [blame]450 not an ancestor of the local ref used to overwrite it.
Junio C Hamano40f2f8d2006-02-07 08:04:39[diff] [blame]451 This flag disables the check. This can cause the
452 remote repository to lose commits; use it with care.
453</p>
454</dd>
Junio C Hamano1ce39ab2007-01-16 22:05:10[diff] [blame]455<dt>
Junio C Hamanoa476efa2008-10-10 15:31:42[diff] [blame]456--repo=&lt;repository&gt;
Junio C Hamano1ce39ab2007-01-16 22:05:10[diff] [blame]457</dt>
458<dd>
459<p>
Junio C Hamanoa476efa2008-10-10 15:31:42[diff] [blame]460 This option is only relevant if no &lt;repository&gt; argument is
461 passed in the invocation. In this case, <em>git-push</em> derives the
462 remote name from the current branch: If it tracks a remote
463 branch, then that remote repository is pushed to. Otherwise,
464 the name "origin" is used. For this latter case, this option
465 can be used to override the name "origin". In other words,
466 the difference between these two commands
Junio C Hamano1ce39ab2007-01-16 22:05:10[diff] [blame]467</p>
Junio C Hamanoa476efa2008-10-10 15:31:42[diff] [blame]468<div class="listingblock">
469<div class="content">
470<pre><tt>git push public #1
471git push --repo=public #2</tt></pre>
472</div></div>
473<div class="para"><p>is that #1 always pushes to "public" whereas #2 pushes to "public"
474only if the current branch does not track a remote branch. This is
475useful if you write an alias or script around <em>git-push</em>.</p></div>
Junio C Hamano1ce39ab2007-01-16 22:05:10[diff] [blame]476</dd>
477<dt>
Junio C Hamanoeb415992008-06-08 22:49:47[diff] [blame]478--thin
479</dt>
480<dt>
481--no-thin
Junio C Hamano1ce39ab2007-01-16 22:05:10[diff] [blame]482</dt>
483<dd>
484<p>
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]485 These options are passed to <em>git-send-pack</em>. Thin
Junio C Hamano1ce39ab2007-01-16 22:05:10[diff] [blame]486 transfer spends extra cycles to minimize the number of
487 objects to be sent and meant to be used on slower connection.
488</p>
489</dd>
490<dt>
Junio C Hamanoeb415992008-06-08 22:49:47[diff] [blame]491-v
492</dt>
493<dt>
494--verbose
Junio C Hamano1ce39ab2007-01-16 22:05:10[diff] [blame]495</dt>
496<dd>
497<p>
498 Run verbosely.
499</p>
500</dd>
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]501</dl></div>
Junio C Hamano40f2f8d2006-02-07 08:04:39[diff] [blame]502</div>
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]503<h2 id="_git_urls_a_id_urls_a">GIT URLS<a id="URLS"></a></h2>
Junio C Hamano40f2f8d2006-02-07 08:04:39[diff] [blame]504<div class="sectionbody">
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]505<div class="para"><p>One of the following notations can be used
506to name the remote repository:</p></div>
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]507<div class="exampleblock">
508<div class="exampleblock-content">
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]509<div class="ilist"><ul>
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]510<li>
511<p>
512rsync://host.xz/path/to/repo.git/
513</p>
514</li>
515<li>
516<p>
Junio C Hamanoa3bb6eb2009-02-05 01:26:33[diff] [blame]517http://host.xz&#91;:port&#93;/path/to/repo.git/
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]518</p>
519</li>
520<li>
521<p>
Junio C Hamanoa3bb6eb2009-02-05 01:26:33[diff] [blame]522https://host.xz&#91;:port&#93;/path/to/repo.git/
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]523</p>
524</li>
525<li>
526<p>
Junio C Hamanoa3bb6eb2009-02-05 01:26:33[diff] [blame]527git://host.xz&#91;:port&#93;/path/to/repo.git/
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]528</p>
529</li>
530<li>
531<p>
Junio C Hamanoa3bb6eb2009-02-05 01:26:33[diff] [blame]532git://host.xz&#91;:port&#93;/~user/path/to/repo.git/
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]533</p>
534</li>
535<li>
536<p>
Junio C Hamanodbb64592007-09-01 11:17:39[diff] [blame]537ssh://&#91;user@&#93;host.xz&#91;:port&#93;/path/to/repo.git/
538</p>
539</li>
540<li>
541<p>
Junio C Hamano7ccb9fd2006-07-15 01:38:40[diff] [blame]542ssh://&#91;user@&#93;host.xz/path/to/repo.git/
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]543</p>
544</li>
545<li>
546<p>
Junio C Hamano7ccb9fd2006-07-15 01:38:40[diff] [blame]547ssh://&#91;user@&#93;host.xz/~user/path/to/repo.git/
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]548</p>
549</li>
550<li>
551<p>
Junio C Hamano7ccb9fd2006-07-15 01:38:40[diff] [blame]552ssh://&#91;user@&#93;host.xz/~/path/to/repo.git
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]553</p>
554</li>
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]555</ul></div>
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]556</div></div>
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]557<div class="para"><p>SSH is the default transport protocol over the network. You can
Junio C Hamanob1d6e882007-08-11 08:30:16[diff] [blame]558optionally specify which user to log-in as, and an alternate,
559scp-like syntax is also supported. Both syntaxes support
Junio C Hamanodbb64592007-09-01 11:17:39[diff] [blame]560username expansion, as does the native git protocol, but
561only the former supports port specification. The following
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]562three are identical to the last three above, respectively:</p></div>
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]563<div class="exampleblock">
564<div class="exampleblock-content">
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]565<div class="ilist"><ul>
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]566<li>
567<p>
Junio C Hamano7ccb9fd2006-07-15 01:38:40[diff] [blame]568&#91;user@&#93;host.xz:/path/to/repo.git/
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]569</p>
570</li>
571<li>
572<p>
Junio C Hamano7ccb9fd2006-07-15 01:38:40[diff] [blame]573&#91;user@&#93;host.xz:~user/path/to/repo.git/
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]574</p>
575</li>
576<li>
577<p>
Junio C Hamano7ccb9fd2006-07-15 01:38:40[diff] [blame]578&#91;user@&#93;host.xz:path/to/repo.git
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]579</p>
580</li>
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]581</ul></div>
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]582</div></div>
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]583<div class="para"><p>To sync with a local directory, you can use:</p></div>
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]584<div class="exampleblock">
585<div class="exampleblock-content">
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]586<div class="ilist"><ul>
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]587<li>
588<p>
589/path/to/repo.git/
590</p>
591</li>
Junio C Hamanob1d6e882007-08-11 08:30:16[diff] [blame]592<li>
593<p>
594file:///path/to/repo.git/
595</p>
596</li>
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]597</ul></div>
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]598</div></div>
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]599<div class="para"><p>They are mostly equivalent, except when cloning. See
600<a href="git-clone.html">git-clone(1)</a> for details.</p></div>
601<div class="para"><p>If there are a large number of similarly-named remote repositories and
Junio C Hamano24bc09a2008-02-28 00:27:44[diff] [blame]602you want to use a different format for them (such that the URLs you
603use will be rewritten into URLs that work), you can create a
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]604configuration section of the form:</p></div>
Junio C Hamano24bc09a2008-02-28 00:27:44[diff] [blame]605<div class="listingblock">
606<div class="content">
607<pre><tt> [url "&lt;actual url base&gt;"]
608 insteadOf = &lt;other url base&gt;</tt></pre>
609</div></div>
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]610<div class="para"><p>For example, with this:</p></div>
Junio C Hamano24bc09a2008-02-28 00:27:44[diff] [blame]611<div class="listingblock">
612<div class="content">
613<pre><tt> [url "git://git.host.xz/"]
614 insteadOf = host.xz:/path/to/
615 insteadOf = work:</tt></pre>
616</div></div>
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]617<div class="para"><p>a URL like "work:repo.git" or like "host.xz:/path/to/repo.git" will be
618rewritten in any context that takes a URL to be "git://git.host.xz/repo.git".</p></div>
Junio C Hamano40f2f8d2006-02-07 08:04:39[diff] [blame]619</div>
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]620<h2 id="_remotes_a_id_remotes_a">REMOTES<a id="REMOTES"></a></h2>
Junio C Hamano40f2f8d2006-02-07 08:04:39[diff] [blame]621<div class="sectionbody">
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]622<div class="para"><p>The name of one of the following can be used instead
623of a URL as <tt>&lt;repository&gt;</tt> argument:</p></div>
624<div class="ilist"><ul>
Junio C Hamano054ea082008-06-01 08:26:34[diff] [blame]625<li>
626<p>
627a remote in the git configuration file: <tt>$GIT_DIR/config</tt>,
628</p>
629</li>
630<li>
631<p>
632a file in the <tt>$GIT_DIR/remotes</tt> directory, or
633</p>
634</li>
635<li>
636<p>
637a file in the <tt>$GIT_DIR/branches</tt> directory.
638</p>
639</li>
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]640</ul></div>
641<div class="para"><p>All of these also allow you to omit the refspec from the command line
642because they each contain a refspec which git will use by default.</p></div>
643<h3 id="_named_remote_in_configuration_file">Named remote in configuration file</h3><div style="clear:left"></div>
644<div class="para"><p>You can choose to provide the name of a remote which you had previously
Junio C Hamano054ea082008-06-01 08:26:34[diff] [blame]645configured using <a href="git-remote.html">git-remote(1)</a>, <a href="git-config.html">git-config(1)</a>
646or even by a manual edit to the <tt>$GIT_DIR/config</tt> file. The URL of
647this remote will be used to access the repository. The refspec
648of this remote will be used by default when you do
649not provide a refspec on the command line. The entry in the
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]650config file would appear like this:</p></div>
Junio C Hamano054ea082008-06-01 08:26:34[diff] [blame]651<div class="listingblock">
652<div class="content">
653<pre><tt> [remote "&lt;name&gt;"]
654 url = &lt;url&gt;
Junio C Hamano0e88f3e2009-06-21 08:03:25[diff] [blame^]655 pushurl = &lt;pushurl&gt;
Junio C Hamano054ea082008-06-01 08:26:34[diff] [blame]656 push = &lt;refspec&gt;
657 fetch = &lt;refspec&gt;</tt></pre>
658</div></div>
Junio C Hamano0e88f3e2009-06-21 08:03:25[diff] [blame^]659<div class="para"><p>The <tt>&lt;pushurl&gt;</tt> is used for pushes only. It is optional and defaults
660to <tt>&lt;url&gt;</tt>.</p></div>
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]661<h3 id="_named_file_in_tt_git_dir_remotes_tt">Named file in <tt>$GIT_DIR/remotes</tt></h3><div style="clear:left"></div>
662<div class="para"><p>You can choose to provide the name of a
Junio C Hamano054ea082008-06-01 08:26:34[diff] [blame]663file in <tt>$GIT_DIR/remotes</tt>. The URL
664in this file will be used to access the repository. The refspec
665in this file will be used as default when you do not
666provide a refspec on the command line. This file should have the
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]667following format:</p></div>
Junio C Hamano1caaf472006-12-31 08:29:35[diff] [blame]668<div class="listingblock">
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]669<div class="content">
Junio C Hamanod3361ad2007-01-01 03:20:24[diff] [blame]670<pre><tt> URL: one of the above URL format
671 Push: &lt;refspec&gt;
672 Pull: &lt;refspec&gt;
673</tt></pre>
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]674</div></div>
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]675<div class="para"><p><tt>Push:</tt> lines are used by <em>git-push</em> and
676<tt>Pull:</tt> lines are used by <em>git-pull</em> and <em>git-fetch</em>.
Junio C Hamano054ea082008-06-01 08:26:34[diff] [blame]677Multiple <tt>Push:</tt> and <tt>Pull:</tt> lines may
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]678be specified for additional branch mappings.</p></div>
679<h3 id="_named_file_in_tt_git_dir_branches_tt">Named file in <tt>$GIT_DIR/branches</tt></h3><div style="clear:left"></div>
680<div class="para"><p>You can choose to provide the name of a
Junio C Hamano054ea082008-06-01 08:26:34[diff] [blame]681file in <tt>$GIT_DIR/branches</tt>.
682The URL in this file will be used to access the repository.
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]683This file should have the following format:</p></div>
Junio C Hamano1caaf472006-12-31 08:29:35[diff] [blame]684<div class="listingblock">
Junio C Hamano249572f2006-10-24 05:44:08[diff] [blame]685<div class="content">
Junio C Hamano054ea082008-06-01 08:26:34[diff] [blame]686<pre><tt> &lt;url&gt;#&lt;head&gt;</tt></pre>
Junio C Hamano249572f2006-10-24 05:44:08[diff] [blame]687</div></div>
Junio C Hamano28363492008-11-14 08:26:31[diff] [blame]688<div class="para"><p><tt>&lt;url&gt;</tt> is required; <tt>#&lt;head&gt;</tt> is optional.</p></div>
689<div class="para"><p>Depending on the operation, git will use one of the following
690refspecs, if you don't provide one on the command line.
691<tt>&lt;branch&gt;</tt> is the name of this file in <tt>$GIT_DIR/branches</tt> and
692<tt>&lt;head&gt;</tt> defaults to <tt>master</tt>.</p></div>
693<div class="para"><p>git fetch uses:</p></div>
Junio C Hamano1caaf472006-12-31 08:29:35[diff] [blame]694<div class="listingblock">
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]695<div class="content">
Junio C Hamano28363492008-11-14 08:26:31[diff] [blame]696<pre><tt> refs/heads/&lt;head&gt;:refs/heads/&lt;branch&gt;</tt></pre>
697</div></div>
698<div class="para"><p>git push uses:</p></div>
699<div class="listingblock">
700<div class="content">
701<pre><tt> HEAD:refs/heads/&lt;head&gt;</tt></pre>
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]702</div></div>
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]703</div>
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]704<h2 id="_output">OUTPUT</h2>
Junio C Hamano6d559fc2008-02-20 10:44:26[diff] [blame]705<div class="sectionbody">
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]706<div class="para"><p>The output of "git push" depends on the transport method used; this
Junio C Hamano6d559fc2008-02-20 10:44:26[diff] [blame]707section describes the output when pushing over the git protocol (either
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]708locally or via ssh).</p></div>
709<div class="para"><p>The status of the push is output in tabular form, with each line
710representing the status of a single ref. Each line is of the form:</p></div>
Junio C Hamano6d559fc2008-02-20 10:44:26[diff] [blame]711<div class="listingblock">
712<div class="content">
713<pre><tt> &lt;flag&gt; &lt;summary&gt; &lt;from&gt; -&gt; &lt;to&gt; (&lt;reason&gt;)</tt></pre>
714</div></div>
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]715<div class="vlist"><dl>
Junio C Hamano6d559fc2008-02-20 10:44:26[diff] [blame]716<dt>
717flag
718</dt>
719<dd>
720<p>
721 A single character indicating the status of the ref. This is
722 blank for a successfully pushed ref, <tt>!</tt> for a ref that was
723 rejected or failed to push, and <em>=</em> for a ref that was up to
724 date and did not need pushing (note that the status of up to
725 date refs is shown only when <tt>git push</tt> is running verbosely).
726</p>
727</dd>
728<dt>
729summary
730</dt>
731<dd>
732<p>
733 For a successfully pushed ref, the summary shows the old and new
734 values of the ref in a form suitable for using as an argument to
735 <tt>git log</tt> (this is <tt>&lt;old&gt;..&lt;new&gt;</tt> in most cases, and
736 <tt>&lt;old&gt;&#8230;&lt;new&gt;</tt> for forced non-fast forward updates). For a
737 failed update, more details are given for the failure.
738 The string <tt>rejected</tt> indicates that git did not try to send the
739 ref at all (typically because it is not a fast forward). The
740 string <tt>remote rejected</tt> indicates that the remote end refused
741 the update; this rejection is typically caused by a hook on the
742 remote side. The string <tt>remote failure</tt> indicates that the
743 remote end did not report the successful update of the ref
744 (perhaps because of a temporary error on the remote side, a
745 break in the network connection, or other transient error).
746</p>
747</dd>
748<dt>
749from
750</dt>
751<dd>
752<p>
753 The name of the local ref being pushed, minus its
754 <tt>refs/&lt;type&gt;/</tt> prefix. In the case of deletion, the
755 name of the local ref is omitted.
756</p>
757</dd>
758<dt>
759to
760</dt>
761<dd>
762<p>
763 The name of the remote ref being updated, minus its
764 <tt>refs/&lt;type&gt;/</tt> prefix.
765</p>
766</dd>
767<dt>
768reason
769</dt>
770<dd>
771<p>
772 A human-readable explanation. In the case of successfully pushed
773 refs, no explanation is needed. For a failed ref, the reason for
774 failure is described.
775</p>
776</dd>
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]777</dl></div>
Junio C Hamano6d559fc2008-02-20 10:44:26[diff] [blame]778</div>
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]779<h2 id="_examples">Examples</h2>
Junio C Hamano6926bef2007-06-16 09:54:05[diff] [blame]780<div class="sectionbody">
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]781<div class="vlist"><dl>
Junio C Hamano6926bef2007-06-16 09:54:05[diff] [blame]782<dt>
Junio C Hamanoea82cff2009-03-18 01:54:48[diff] [blame]783git push
784</dt>
785<dd>
786<p>
787 Works like <tt>git push &lt;remote&gt;</tt>, where &lt;remote&gt; is the
788 current branch's remote (or <tt>origin</tt>, if no remote is
789 configured for the current branch).
790</p>
791</dd>
792<dt>
793git push origin
794</dt>
795<dd>
796<p>
797 Without additional configuration, works like
798 <tt>git push origin :</tt>.
799</p>
800<div class="para"><p>The default behavior of this command when no &lt;refspec&gt; is given can be
801configured by setting the <tt>push</tt> option of the remote.</p></div>
802<div class="para"><p>For example, to default to pushing only the current branch to <tt>origin</tt>
803use <tt>git config remote.origin.push HEAD</tt>. Any valid &lt;refspec&gt; (like
804the ones in the examples below) can be configured as the default for
805<tt>git push origin</tt>.</p></div>
806</dd>
807<dt>
808git push origin :
809</dt>
810<dd>
811<p>
812 Push "matching" branches to <tt>origin</tt>. See
813 &lt;refspec&gt; in the <a href="#OPTIONS">OPTIONS</a> section above for a
814 description of "matching" branches.
815</p>
816</dd>
817<dt>
Junio C Hamano6926bef2007-06-16 09:54:05[diff] [blame]818git push origin master
819</dt>
820<dd>
821<p>
822 Find a ref that matches <tt>master</tt> in the source repository
823 (most likely, it would find <tt>refs/heads/master</tt>), and update
824 the same ref (e.g. <tt>refs/heads/master</tt>) in <tt>origin</tt> repository
Junio C Hamanoa9aee782008-04-23 16:09:20[diff] [blame]825 with it. If <tt>master</tt> did not exist remotely, it would be
826 created.
Junio C Hamano6926bef2007-06-16 09:54:05[diff] [blame]827</p>
828</dd>
829<dt>
Junio C Hamano8b6e23b2009-02-01 06:36:08[diff] [blame]830git push origin HEAD
Junio C Hamano6926bef2007-06-16 09:54:05[diff] [blame]831</dt>
832<dd>
833<p>
Junio C Hamano8b6e23b2009-02-01 06:36:08[diff] [blame]834 A handy way to push the current branch to the same name on the
835 remote.
Junio C Hamano6926bef2007-06-16 09:54:05[diff] [blame]836</p>
837</dd>
838<dt>
Junio C Hamano7f80ae82008-07-30 18:31:35[diff] [blame]839git push origin master:satellite/master dev:satellite/dev
Junio C Hamano6926bef2007-06-16 09:54:05[diff] [blame]840</dt>
841<dd>
842<p>
Junio C Hamano7f80ae82008-07-30 18:31:35[diff] [blame]843 Use the source ref that matches <tt>master</tt> (e.g. <tt>refs/heads/master</tt>)
844 to update the ref that matches <tt>satellite/master</tt> (most probably
845 <tt>refs/remotes/satellite/master</tt>) in the <tt>origin</tt> repository, then
846 do the same for <tt>dev</tt> and <tt>satellite/dev</tt>.
Junio C Hamano6926bef2007-06-16 09:54:05[diff] [blame]847</p>
848</dd>
Junio C Hamanobfd4f9a2007-09-06 08:52:44[diff] [blame]849<dt>
Junio C Hamano8b6e23b2009-02-01 06:36:08[diff] [blame]850git push origin HEAD:master
851</dt>
852<dd>
853<p>
854 Push the current branch to the remote ref matching <tt>master</tt> in the
855 <tt>origin</tt> repository. This form is convenient to push the current
856 branch without thinking about its local name.
857</p>
858</dd>
859<dt>
Junio C Hamanobfd4f9a2007-09-06 08:52:44[diff] [blame]860git push origin master:refs/heads/experimental
861</dt>
862<dd>
863<p>
864 Create the branch <tt>experimental</tt> in the <tt>origin</tt> repository
Junio C Hamanoa9aee782008-04-23 16:09:20[diff] [blame]865 by copying the current <tt>master</tt> branch. This form is only
866 needed to create a new branch or tag in the remote repository when
867 the local name and the remote name are different; otherwise,
868 the ref name on its own will work.
Junio C Hamanobfd4f9a2007-09-06 08:52:44[diff] [blame]869</p>
870</dd>
Junio C Hamano8b6e23b2009-02-01 06:36:08[diff] [blame]871<dt>
872git push origin :experimental
873</dt>
874<dd>
875<p>
876 Find a ref that matches <tt>experimental</tt> in the <tt>origin</tt> repository
877 (e.g. <tt>refs/heads/experimental</tt>), and delete it.
878</p>
879</dd>
Junio C Hamanod533bdb2009-02-25 09:56:58[diff] [blame]880<dt>
881git push origin &#43;dev:master
882</dt>
883<dd>
884<p>
885 Update the origin repository's master branch with the dev branch,
886 allowing non-fast forward updates. <strong>This can leave unreferenced
887 commits dangling in the origin repository.</strong> Consider the
888 following situation, where a fast forward is not possible:
889</p>
890<div class="listingblock">
891<div class="content">
892<pre><tt> o---o---o---A---B origin/master
893 \
894 X---Y---Z dev</tt></pre>
895</div></div>
896<div class="para"><p>The above command would change the origin repository to</p></div>
897<div class="listingblock">
898<div class="content">
899<pre><tt> A---B (unnamed branch)
900 /
901 o---o---o---X---Y---Z master</tt></pre>
902</div></div>
903<div class="para"><p>Commits A and B would no longer belong to a branch with a symbolic name,
904and so would be unreachable. As such, these commits would be removed by
905a <tt>git gc</tt> command on the origin repository.</p></div>
906</dd>
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]907</dl></div>
Junio C Hamano6926bef2007-06-16 09:54:05[diff] [blame]908</div>
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]909<h2 id="_author">Author</h2>
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]910<div class="sectionbody">
Junio C Hamano0868a302008-07-22 09:20:44[diff] [blame]911<div class="para"><p>Written by Junio C Hamano &lt;gitster@pobox.com&gt;, later rewritten in C
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]912by Linus Torvalds &lt;torvalds@osdl.org&gt;</p></div>
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]913</div>
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]914<h2 id="_documentation">Documentation</h2>
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]915<div class="sectionbody">
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]916<div class="para"><p>Documentation by Junio C Hamano and the git-list &lt;git@vger.kernel.org&gt;.</p></div>
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]917</div>
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]918<h2 id="_git">GIT</h2>
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]919<div class="sectionbody">
Junio C Hamanoba4b9282008-07-06 05:20:31[diff] [blame]920<div class="para"><p>Part of the <a href="git.html">git(1)</a> suite</p></div>
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]921</div>
922<div id="footer">
923<div id="footer-text">
Junio C Hamano0e88f3e2009-06-21 08:03:25[diff] [blame^]924Last updated 2009-06-21 08:03:01 UTC
Junio C Hamano1a4e8412005-12-27 08:17:23[diff] [blame]925</div>
926</div>
927</body>
928</html>