7e9452efe1f82a34fb5d2e5eff847bd93a1260f6
   1git-push(1)
   2===========
   3
   4NAME
   5----
   6git-push - Update remote refs along with associated objects.
   7
   8
   9SYNOPSIS
  10--------
  11'git-push' [--all] [--tags] [--force] <repository> <refspec>...
  12
  13DESCRIPTION
  14-----------
  15
  16Updates remote refs using local refs, while sending objects
  17necessary to complete the given refs.
  18
  19You can make "interesting" things to happen on the repository
  20every time you push into it, by setting up 'hooks' there.  See
  21documentation for gitlink:git-receive-pack[1].
  22
  23
  24OPTIONS
  25-------
  26<repository>::
  27        The "remote" repository that is destination of a push operation.
  28include::urls.txt[]
  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+
  36The <src> side can be an
  37arbitrary "SHA1 expression" that can be used as an
  38argument to `git-cat-file -t`.  E.g. `master~4` (push
  39four parents before the current master head).
  40+
  41The local ref that matches <src> is used
  42to fast forward the remote ref that matches <dst>.  If
  43the optional plus `+` is used, the remote ref is updated
  44even if it does not result in a fast forward update.
  45+
  46Some short-cut notations are also supported.
  47+
  48* `tag <tag>` means the same as `refs/tags/<tag>:refs/tags/<tag>`.
  49* A parameter <ref> without a colon is equivalent to
  50  <ref>`:`<ref>, hence updates <ref> in the destination from <ref>
  51  in the source.
  52
  53\--all::
  54        Instead of naming each ref to push, specifies all refs
  55        to be pushed.
  56
  57\--tags::
  58        All refs under `$GIT_DIR/refs/tags` are pushed, in
  59        addition to refspecs explicitly listed on the command
  60        line.
  61
  62-f, \--force::
  63        Usually, the command refuses to update a remote ref that is
  64        not a descendent of the local ref used to overwrite it.
  65        This flag disables the check.  This can cause the
  66        remote repository to lose commits; use it with care.
  67
  68
  69Author
  70------
  71Written by Junio C Hamano <junkio@cox.net>
  72
  73Documentation
  74--------------
  75Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>.
  76
  77GIT
  78---
  79Part of the gitlink:git[7] suite
  80