receive-pack: implement advertising and receiving push options
The pre/post receive hook may be interested in more information from the user. This information can be transmitted when both client and server support the "push-options" capability, which when used is a phase directly after update commands ended by a flush pkt. Similar to the atomic option, the server capability can be disabled via the `receive.advertisePushOptions` config variable. While documenting this, fix a nit in the `receive.advertiseAtomic` wording. Signed-off-by: Stefan Beller <sbeller@google.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:

committed by
Junio C Hamano

parent
77a9745d19
commit
c714e45f87
@ -253,6 +253,15 @@ atomic pushes. If the pushing client requests this capability, the server
|
||||
will update the refs in one atomic transaction. Either all refs are
|
||||
updated or none.
|
||||
|
||||
push-options
|
||||
------------
|
||||
|
||||
If the server sends the 'push-options' capability it is able to accept
|
||||
push options after the update commands have been sent, but before the
|
||||
packfile is streamed. If the pushing client requests this capability,
|
||||
the server will pass the options to the pre- and post- receive hooks
|
||||
that process this push request.
|
||||
|
||||
allow-tip-sha1-in-want
|
||||
----------------------
|
||||
|
||||
|
Reference in New Issue
Block a user