2005-09-08 00:26:23 +00:00
|
|
|
git-push(1)
|
|
|
|
|
===========
|
2005-08-23 08:49:47 +00:00
|
|
|
|
|
|
|
|
NAME
|
|
|
|
|
----
|
2006-03-09 16:24:50 +00:00
|
|
|
git-push - Update remote refs along with associated objects
|
2005-08-23 08:49:47 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
SYNOPSIS
|
|
|
|
|
--------
|
2006-01-16 07:27:34 +00:00
|
|
|
'git-push' [--all] [--tags] [--force] <repository> <refspec>...
|
2005-08-23 08:49:47 +00:00
|
|
|
|
|
|
|
|
DESCRIPTION
|
|
|
|
|
-----------
|
2005-08-24 23:23:08 +00:00
|
|
|
|
|
|
|
|
Updates remote refs using local refs, while sending objects
|
|
|
|
|
necessary to complete the given refs.
|
2005-08-23 08:49:47 +00:00
|
|
|
|
2006-02-06 00:42:27 +00:00
|
|
|
You can make interesting things happen to a repository
|
2005-12-05 08:32:01 +00:00
|
|
|
every time you push into it, by setting up 'hooks' there. See
|
|
|
|
|
documentation for gitlink:git-receive-pack[1].
|
|
|
|
|
|
2005-08-23 08:49:47 +00:00
|
|
|
|
|
|
|
|
OPTIONS
|
|
|
|
|
-------
|
2006-02-05 22:43:47 +00:00
|
|
|
<repository>::
|
2006-02-05 23:29:49 +00:00
|
|
|
The "remote" repository that is destination of a push
|
|
|
|
|
operation. See the section <<URLS,GIT URLS>> below.
|
2006-02-05 22:43:47 +00:00
|
|
|
|
|
|
|
|
<refspec>::
|
|
|
|
|
The canonical format of a <refspec> parameter is
|
|
|
|
|
`+?<src>:<dst>`; that is, an optional plus `+`, followed
|
|
|
|
|
by the source ref, followed by a colon `:`, followed by
|
|
|
|
|
the destination ref.
|
|
|
|
|
+
|
|
|
|
|
The <src> side can be an
|
|
|
|
|
arbitrary "SHA1 expression" that can be used as an
|
|
|
|
|
argument to `git-cat-file -t`. E.g. `master~4` (push
|
|
|
|
|
four parents before the current master head).
|
|
|
|
|
+
|
|
|
|
|
The local ref that matches <src> is used
|
|
|
|
|
to fast forward the remote ref that matches <dst>. If
|
|
|
|
|
the optional plus `+` is used, the remote ref is updated
|
|
|
|
|
even if it does not result in a fast forward update.
|
|
|
|
|
+
|
2006-02-22 04:28:50 +00:00
|
|
|
Note: If no explicit refspec is found, (that is neither
|
|
|
|
|
on the command line nor in any Push line of the
|
|
|
|
|
corresponding remotes file---see below), then all the
|
|
|
|
|
refs that exist both on the local side and on the remote
|
|
|
|
|
side are updated.
|
|
|
|
|
+
|
2006-02-05 22:43:47 +00:00
|
|
|
Some short-cut notations are also supported.
|
|
|
|
|
+
|
|
|
|
|
* `tag <tag>` means the same as `refs/tags/<tag>:refs/tags/<tag>`.
|
|
|
|
|
* A parameter <ref> without a colon is equivalent to
|
|
|
|
|
<ref>`:`<ref>, hence updates <ref> in the destination from <ref>
|
|
|
|
|
in the source.
|
2005-08-23 08:49:47 +00:00
|
|
|
|
2005-10-20 04:25:39 +00:00
|
|
|
\--all::
|
2006-02-06 00:42:27 +00:00
|
|
|
Instead of naming each ref to push, specifies that all
|
|
|
|
|
refs be pushed.
|
2005-10-20 04:25:39 +00:00
|
|
|
|
2006-01-16 07:27:34 +00:00
|
|
|
\--tags::
|
|
|
|
|
All refs under `$GIT_DIR/refs/tags` are pushed, in
|
|
|
|
|
addition to refspecs explicitly listed on the command
|
|
|
|
|
line.
|
|
|
|
|
|
2005-10-20 04:25:39 +00:00
|
|
|
-f, \--force::
|
2006-01-30 01:40:50 +00:00
|
|
|
Usually, the command refuses to update a remote ref that is
|
|
|
|
|
not a descendent of the local ref used to overwrite it.
|
|
|
|
|
This flag disables the check. This can cause the
|
|
|
|
|
remote repository to lose commits; use it with care.
|
2005-08-23 08:49:47 +00:00
|
|
|
|
2006-02-05 23:29:49 +00:00
|
|
|
include::urls.txt[]
|
2005-12-05 08:32:01 +00:00
|
|
|
|
2005-08-23 08:49:47 +00:00
|
|
|
Author
|
|
|
|
|
------
|
|
|
|
|
Written by Junio C Hamano <junkio@cox.net>
|
|
|
|
|
|
|
|
|
|
Documentation
|
|
|
|
|
--------------
|
|
|
|
|
Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>.
|
|
|
|
|
|
|
|
|
|
GIT
|
|
|
|
|
---
|
2005-09-19 10:10:51 +00:00
|
|
|
Part of the gitlink:git[7] suite
|
2005-08-23 08:49:47 +00:00
|
|
|
|
