table of contents
other versions
- jessie 1:2.1.4-2.1+deb8u6
- jessie-backports 1:2.11.0-3~bpo8+1
- 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.21.0+next.20190320-1
GIT-RECEIVE-PACK(1) | Git Manual | GIT-RECEIVE-PACK(1) |
NAME¶
git-receive-pack - Receive what is pushed into the repositorySYNOPSIS¶
git-receive-pack <directory>
DESCRIPTION¶
Invoked by git send-pack and updates the repository with the information fed from the remote end. This command is usually not invoked directly by the end user. The UI for the protocol is on the git send-pack side, and the program pair is meant to be used to push updates to remote repository. For pull operations, see git-fetch-pack(1). The command allows for creation and fast-forwarding of sha1 refs (heads/tags) on the remote end (strictly speaking, it is the local end git-receive-pack runs, but to the user who is sitting at the send-pack end, it is updating the remote. Confused?) There are other real-world examples of using update and post-update hooks found in the Documentation/howto directory. git-receive-pack honours the receive.denyNonFastForwards config option, which tells it if updates to a ref should be denied if they are not fast-forwards. A number of other receive.* config options are available to tweak its behavior, see git-config(1).OPTIONS¶
<directory>The repository to sync into.
PRE-RECEIVE HOOK¶
Before any ref is updated, if $GIT_DIR/hooks/pre-receive file exists and is executable, it will be invoked once with no parameters. The standard input of the hook will be one line per ref to be updated:sha1-old SP sha1-new SP refname LF
The name and the e-mail address of the owner of the key
that signed the push certificate.
GIT_PUSH_CERT_KEY
The GPG key ID of the key that signed the push
certificate.
GIT_PUSH_CERT_STATUS
The status of GPG verification of the push certificate,
using the same mnemonic as used in %G? format of git log family
of commands (see git-log(1)).
GIT_PUSH_CERT_NONCE
The nonce string the process asked the signer to include
in the push certificate. If this does not match the value recorded on the
"nonce" header in the push certificate, it may indicate that the
certificate is a valid one that is being replayed from a separate "git
push" session.
GIT_PUSH_CERT_NONCE_STATUS
UNSOLICITED
GIT_PUSH_CERT_NONCE_SLOP
"git push --signed" sent a nonce when we did
not ask it to send one.
MISSING
"git push --signed" did not send any nonce
header.
BAD
"git push --signed" sent a bogus nonce.
OK
"git push --signed" sent the nonce we asked it
to send.
SLOP
"git push --signed" sent a nonce different from
what we asked it to send now, but in a previous session. See
GIT_PUSH_CERT_NONCE_SLOP environment variable.
"git push --signed" sent a nonce different from
what we asked it to send now, but in a different session whose starting time
is different by this many seconds from the current session. Only meaningful
when GIT_PUSH_CERT_NONCE_STATUS says SLOP. Also read about
receive.certNonceSlop variable in git-config(1).
This hook is called before any refname is updated and before any fast-forward
checks are performed.
If the pre-receive hook exits with a non-zero exit status no updates will be
performed, and the update, post-receive and post-update hooks will not be
invoked either. This can be useful to quickly bail out if the update is not to
be supported.
UPDATE HOOK¶
Before each ref is updated, if $GIT_DIR/hooks/update file exists and is executable, it is invoked once per ref, with three parameters:$GIT_DIR/hooks/update refname sha1-old sha1-new
POST-RECEIVE HOOK¶
After all refs were updated (or attempted to be updated), if any ref update was successful, and if $GIT_DIR/hooks/post-receive file exists and is executable, it will be invoked once with no parameters. The standard input of the hook will be one line for each successfully updated ref:sha1-old SP sha1-new SP refname LF
#!/bin/sh # mail out commit update information. while read oval nval ref do if expr "$oval" : '0*$' >/dev/null then echo "Created a new ref, with the following commits:" git rev-list --pretty "$nval" else echo "New commits:" git rev-list --pretty "$nval" "^$oval" fi | mail -s "Changes to ref $ref" commit-list@mydomain done # log signed push certificate, if any if test -n "${GIT_PUSH_CERT-}" && test ${GIT_PUSH_CERT_STATUS} = G then ( echo expected nonce is ${GIT_PUSH_NONCE} git cat-file blob ${GIT_PUSH_CERT} ) | mail -s "push certificate from $GIT_PUSH_CERT_SIGNER" push-log@mydomain fi exit 0
POST-UPDATE HOOK¶
After all other processing, if at least one ref was updated, and if $GIT_DIR/hooks/post-update file exists and is executable, then post-update will be called with the list of refs that have been updated. This can be used to implement any repository wide cleanup tasks. The exit code from this hook invocation is ignored; the only thing left for git-receive-pack to do at that point is to exit itself anyway. This hook can be used, for example, to run git update-server-info if the repository is packed and is served via a dumb transport.#!/bin/sh exec git update-server-info
SEE ALSO¶
git-send-pack(1), gitnamespaces(7)GIT¶
Part of the git(1) suite05/15/2017 | Git 2.11.0 |