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