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.OPTIONS
--allDo 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.
--force
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 care.
--dry-run
Do everything except actually send the
updates.
--verbose
Report the list of objects being walked
locally and the list of objects successfully sent to the remote
repository.
-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:
<ref>...
•Remote HEAD must resolve to an object
that exists locally
•Specified branch resolves to an object
that exists locally
•Specified branch is an ancestor of the
remote HEAD
The remote refs to update.
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>.•It is an error if <src>
does not match exactly one of the local refs.
•If <dst> does not match
any remote ref, either
•it has to start with
"refs/"; <dst> is used as the destination literally in this
case.
•<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 destination.
GIT
Part of the git(1) suite02/28/2023 | Git 2.39.2 |