1GIT-HTTP-PUSH(1)                  Git Manual                  GIT-HTTP-PUSH(1)
2
3
4

NAME

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

SYNOPSIS

9       git http-push [--all] [--dry-run] [--force] [--verbose] <URL> <ref> [<ref>...]
10

DESCRIPTION

12       Sends missing objects to remote repository, and updates the remote
13       branch.
14
15       NOTE: This command is temporarily disabled if your libcurl is older
16       than 7.16, as the combination has been reported not to work and
17       sometimes corrupts repository.
18

OPTIONS

20       --all
21           Do not assume that the remote repository is complete in its current
22           state, and verify all objects in the entire local ref’s history
23           exist in the remote repository.
24
25       --force
26           Usually, the command refuses to update a remote ref that is not an
27           ancestor of the local ref used to overwrite it. This flag disables
28           the check. What this means is that the remote repository can lose
29           commits; use it with care.
30
31       --dry-run
32           Do everything except actually send the updates.
33
34       --verbose
35           Report the list of objects being walked locally and the list of
36           objects successfully sent to the remote repository.
37
38       -d, -D
39           Remove <ref> from remote repository. The specified branch cannot be
40           the remote HEAD. If -d is specified the following other conditions
41           must also be met:
42
43           •   Remote HEAD must resolve to an object that exists locally
44
45           •   Specified branch resolves to an object that exists locally
46
47           •   Specified branch is an ancestor of the remote HEAD
48
49       <ref>...
50           The remote refs to update.
51

SPECIFYING THE REFS

53       A <ref> specification can be either a single pattern, or a pair of such
54       patterns separated by a colon ":" (this means that a ref name cannot
55       have a colon in it). A single pattern <name> is just a shorthand for
56       <name>:<name>.
57
58       Each pattern pair <src>:<dst> consists of the source side (before the
59       colon) and the destination side (after the colon). The ref to be pushed
60       is determined by finding a match that matches the source side, and
61       where it is pushed is determined by using the destination side.
62
63       •   It is an error if <src> does not match exactly one of the local
64           refs.
65
66       •   If <dst> does not match any remote ref, either
67
68           •   it has to start with "refs/"; <dst> is used as the destination
69               literally in this case.
70
71           •   <src> == <dst> and the ref that matched the <src> must not
72               exist in the set of remote refs; the ref matched <src> locally
73               is used as the name of the destination.
74
75       Without --force, the <src> ref is stored at the remote only if <dst>
76       does not exist, or <dst> is a proper subset (i.e. an ancestor) of
77       <src>. This check, known as "fast-forward check", is performed in order
78       to avoid accidentally overwriting the remote ref and lose other
79       peoples' commits from there.
80
81       With --force, the fast-forward check is disabled for all refs.
82
83       Optionally, a <ref> parameter can be prefixed with a plus + sign to
84       disable the fast-forward check only on that ref.
85

GIT

87       Part of the git(1) suite
88
89
90
91Git 2.36.1                        2022-05-05                  GIT-HTTP-PUSH(1)