table of contents
- stretch 1:2.11.0-3+deb9u4
- testing 1:2.20.1-2
- stretch-backports 1:2.20.1-1~bpo9+1
- unstable 1:2.20.1-2
- experimental 1:2.22.0+next.20190701-1
GIT-HTTP-PUSH(1) | Git Manual | GIT-HTTP-PUSH(1) |
NAME¶
git-http-push - Push objects over HTTP/DAV to another repositorySYNOPSIS¶
git http-push [--all] [--dry-run] [--force] [--verbose] <url> <ref> [<ref>...]
DESCRIPTION¶
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.
OPTIONS¶
--all--force
--dry-run
--verbose
-d, -D
<ref>...
SPECIFYING THE REFS¶
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.
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 refs.
Optionally, a <ref> parameter can be prefixed with a plus + sign to disable the fast-forward check only on that ref.
GIT¶
Part of the git(1) suite09/28/2018 | Git 2.11.0 |