remote.c: "git-push frotz" should update what matches at the source.
[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
MK
11[verse]
12'git-push' [--all] [--tags] [--receive-pack=<git-receive-pack>]
13 [--repo=all] [-f | --force] [-v] [<repository> <refspec>...]
7fc9d69f
JH
14
15DESCRIPTION
16-----------
ab9b3138
JH
17
18Updates remote refs using local refs, while sending objects
19necessary to complete the given refs.
7fc9d69f 20
cc55aaec 21You can make interesting things happen to a repository
eb0362a4
JH
22every time you push into it, by setting up 'hooks' there. See
23documentation for gitlink:git-receive-pack[1].
24
7fc9d69f
JH
25
26OPTIONS
27-------
3598a308 28<repository>::
85a97d4e
BF
29 The "remote" repository that is destination of a push
30 operation. See the section <<URLS,GIT URLS>> below.
3598a308
BF
31
32<refspec>::
33 The canonical format of a <refspec> parameter is
34 `+?<src>:<dst>`; that is, an optional plus `+`, followed
35 by the source ref, followed by a colon `:`, followed by
36 the destination ref.
37+
38The <src> side can be an
39arbitrary "SHA1 expression" that can be used as an
40argument to `git-cat-file -t`. E.g. `master~4` (push
41four parents before the current master head).
42+
43The local ref that matches <src> is used
44to fast forward the remote ref that matches <dst>. If
45the optional plus `+` is used, the remote ref is updated
46even if it does not result in a fast forward update.
47+
aa064743
CW
48Note: If no explicit refspec is found, (that is neither
49on the command line nor in any Push line of the
50corresponding remotes file---see below), then all the
51refs that exist both on the local side and on the remote
52side are updated.
53+
25fb6290 54`tag <tag>` means the same as `refs/tags/<tag>:refs/tags/<tag>`.
3598a308 55+
25fb6290
JH
56A parameter <ref> without a colon is equivalent to
57<ref>`:`<ref>, hence updates <ref> in the destination from <ref>
58in the source.
59+
60Pushing an empty <src> allows you to delete the <dst> ref from
61the remote repository.
7fc9d69f 62
d6a73596 63\--all::
cc55aaec
BF
64 Instead of naming each ref to push, specifies that all
65 refs be pushed.
d6a73596 66
42301e34
JH
67\--tags::
68 All refs under `$GIT_DIR/refs/tags` are pushed, in
69 addition to refspecs explicitly listed on the command
70 line.
71
d23842fd 72\--receive-pack=<git-receive-pack>::
5214f770
UKK
73 Path to the 'git-receive-pack' program on the remote
74 end. Sometimes useful when pushing to a remote
75 repository over ssh, and you do not have the program in
76 a directory on the default $PATH.
77
d23842fd
UKK
78\--exec=<git-receive-pack>::
79 Same as \--receive-pack=<git-receive-pack>.
80
d6a73596 81-f, \--force::
f0fff36e 82 Usually, the command refuses to update a remote ref that is
addf88e4 83 not a descendant of the local ref used to overwrite it.
f0fff36e
BF
84 This flag disables the check. This can cause the
85 remote repository to lose commits; use it with care.
7fc9d69f 86
dc36f265
JH
87\--repo=<repo>::
88 When no repository is specified the command defaults to
89 "origin"; this overrides it.
90
91\--thin, \--no-thin::
92 These options are passed to `git-send-pack`. Thin
93 transfer spends extra cycles to minimize the number of
94 objects to be sent and meant to be used on slower connection.
95
96-v::
97 Run verbosely.
98
85a97d4e 99include::urls.txt[]
eb0362a4 100
7fc9d69f
JH
101Author
102------
25fb6290
JH
103Written by Junio C Hamano <junkio@cox.net>, later rewritten in C
104by Linus Torvalds <torvalds@osdl.org>
7fc9d69f
JH
105
106Documentation
107--------------
108Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>.
109
110GIT
111---
a7154e91 112Part of the gitlink:git[7] suite