]>
Commit | Line | Data |
---|---|---|
215a7ad1 JH |
1 | git-push(1) |
2 | =========== | |
7fc9d69f JH |
3 | |
4 | NAME | |
5 | ---- | |
215a7ad1 | 6 | git-push - Update remote refs along with associated objects. |
7fc9d69f JH |
7 | |
8 | ||
9 | SYNOPSIS | |
10 | -------- | |
215a7ad1 | 11 | 'git-push' [--all] [--force] <repository> <refspec>... |
7fc9d69f JH |
12 | |
13 | DESCRIPTION | |
14 | ----------- | |
ab9b3138 JH |
15 | |
16 | Updates remote refs using local refs, while sending objects | |
17 | necessary to complete the given refs. | |
7fc9d69f | 18 | |
eb0362a4 JH |
19 | You can make "interesting" things to happen on the repository |
20 | every time you push into it, by setting up 'hooks' there. See | |
21 | documentation for gitlink:git-receive-pack[1]. | |
22 | ||
7fc9d69f JH |
23 | |
24 | OPTIONS | |
25 | ------- | |
ab9b3138 | 26 | include::pull-fetch-param.txt[] |
7fc9d69f | 27 | |
d6a73596 JH |
28 | \--all:: |
29 | Instead of naming each ref to push, specifies all refs | |
30 | to be pushed. | |
31 | ||
32 | -f, \--force:: | |
33 | Usually, the command refuses to update a local ref that is | |
34 | not an ancestor of the remote ref used to overwrite it. | |
35 | This flag disables the check. What this means is that the | |
36 | local repository can lose commits; use it with care. | |
7fc9d69f | 37 | |
eb0362a4 | 38 | |
7fc9d69f JH |
39 | Author |
40 | ------ | |
41 | Written by Junio C Hamano <junkio@cox.net> | |
42 | ||
43 | Documentation | |
44 | -------------- | |
45 | Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>. | |
46 | ||
47 | GIT | |
48 | --- | |
a7154e91 | 49 | Part of the gitlink:git[7] suite |
7fc9d69f | 50 |