[thirdparty/git.git] / Documentation / git-push.txt

git-push(1)
===========

NAME
----
git-push - Update remote refs along with associated objects


SYNOPSIS
--------
'git-push' [--all] [--tags] [--force] <repository> <refspec>...

DESCRIPTION
-----------

Updates remote refs using local refs, while sending objects
necessary to complete the given refs.

You can make interesting things happen to a repository
every time you push into it, by setting up 'hooks' there.  See
documentation for gitlink:git-receive-pack[1].


OPTIONS
-------
<repository>::
	The "remote" repository that is destination of a push
	operation.  See the section <<URLS,GIT URLS>> below.

<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.
+
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.
+
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.

\--all::
	Instead of naming each ref to push, specifies that all
	refs be pushed.

\--tags::
	All refs under `$GIT_DIR/refs/tags` are pushed, in
	addition to refspecs explicitly listed on the command
	line.

-f, \--force::
	Usually, the command refuses to update a remote ref that is
	not a descendant 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.

include::urls.txt[]

Author
------
Written by Junio C Hamano <junkio@cox.net>

Documentation
--------------
Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>.

GIT
---
Part of the gitlink:git[7] suite
Commit	Line	Data
	1	git-push(1)
	2	===========
	3
	4	NAME
	5	----
	6	git-push - Update remote refs along with associated objects
	7
	8
	9	SYNOPSIS
	10	--------
	11	'git-push' [--all] [--tags] [--force] <repository> <refspec>...
	12
	13	DESCRIPTION
	14	-----------
	15
	16	Updates remote refs using local refs, while sending objects
	17	necessary to complete the given refs.
	18
	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].
	22
	23
	24	OPTIONS
	25	-------
	26	<repository>::
	27	The "remote" repository that is destination of a push
	28	operation. See the section <<URLS,GIT URLS>> below.
	29
	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	Some short-cut notations are also supported.
	53	+
	54	* `tag <tag>` means the same as `refs/tags/<tag>:refs/tags/<tag>`.
	55	* A parameter <ref> without a colon is equivalent to
	56	<ref>`:`<ref>, hence updates <ref> in the destination from <ref>
	57	in the source.
	58
	59	\--all::
	60	Instead of naming each ref to push, specifies that all
	61	refs be pushed.
	62
	63	\--tags::
	64	All refs under `$GIT_DIR/refs/tags` are pushed, in
	65	addition to refspecs explicitly listed on the command
	66	line.
	67
	68	-f, \--force::
	69	Usually, the command refuses to update a remote ref that is
	70	not a descendant of the local ref used to overwrite it.
	71	This flag disables the check. This can cause the
	72	remote repository to lose commits; use it with care.
	73
	74	include::urls.txt[]
	75
	76	Author
	77	------
	78	Written by Junio C Hamano <junkio@cox.net>
	79
	80	Documentation
	81	--------------
	82	Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>.
	83
	84	GIT
	85	---
	86	Part of the gitlink:git[7] suite
	87