man pages section 1: User Commands

Exit Print View

Updated: July 2014

git-http-push (1)


git-http-push - Push objects over HTTP/DAV to another repository


git http-push [--all] [--dry-run] [--force] [--verbose] <url> <ref> [<ref>...]


Git Manual                                       GIT-HTTP-PUSH(1)

     git-http-push - Push objects over HTTP/DAV to another

     git http-push [--all] [--dry-run] [--force] [--verbose] <url> <ref> [<ref>...]

     Sends missing objects to remote repository, and updates the
     remote branch.

     NOTE: This command is temporarily disabled if your libcurl
     is older than 7.16, as the combination has been reported not
     to work and sometimes corrupts repository.

         Do not assume that the remote repository is complete in
         its current state, and verify all objects in the entire
         local ref's history exist in the remote repository.

         Usually, the command refuses to update a remote ref that
         is not an ancestor of the local ref used to overwrite
         it. This flag disables the check. What this means is
         that the remote repository can lose commits; use it with

         Do everything except actually send the updates.

         Report the list of objects being walked locally and the
         list of objects successfully sent to the remote

     -d, -D
         Remove <ref> from remote repository. The specified
         branch cannot be the remote HEAD. If -d is specified the
         following other conditions must also be met:

         o   Remote HEAD must resolve to an object that exists

         o   Specified branch resolves to an object that exists

         o   Specified branch is an ancestor of the remote HEAD

         The remote refs to update.

Git          Last change: 02/22/2012                    1

Git Manual                                       GIT-HTTP-PUSH(1)

     A <ref> specification can be either a single pattern, or a
     pair of such patterns separated by a colon ":" (this means
     that a ref name cannot have a colon in it). A single pattern
     <name> is just a shorthand for <name>:<name>.

     Each pattern pair consists of the source side (before the
     colon) and the destination side (after the colon). The ref
     to be pushed is determined by finding a match that matches
     the source side, and where it is pushed is determined by
     using the destination side.

     o   It is an error if <src> does not match exactly one of
         the local refs.

     o   If <dst> does not match any remote ref, either

         o   it has to start with "refs/"; <dst> is used as the
             destination literally in this case.

         o   <src> == <dst> and the ref that matched the <src>
             must not exist in the set of remote refs; the ref
             matched <src> locally is used as the name of the

     Without --force, the <src> ref is stored at the remote only
     if <dst> does not exist, or <dst> is a proper subset (i.e.
     an ancestor) of <src>. This check, known as "fast-forward
     check", is performed in order to avoid accidentally
     overwriting the remote ref and lose other peoples' commits
     from there.

     With --force, the fast-forward check is disabled for all

     Optionally, a <ref> parameter can be prefixed with a plus +
     sign to disable the fast-forward check only on that ref.

     Part of the git(1) suite

     See attributes(5) for descriptions of the following

Git          Last change: 02/22/2012                    2

Git Manual                                       GIT-HTTP-PUSH(1)

     |Availability   | developer/versioning/git |
     |Stability      | Uncommitted              |
     This software was built from source available at  The original
     community source was downloaded from  http://git-

     Further information about this software can be found on the
     open source community website at

Git          Last change: 02/22/2012                    3