Documentation/git-push.txt: document when --signed may fail
Like --atomic, --signed will fail if the server does not advertise the necessary capability. In addition, it requires gpg on the client side. Signed-off-by: Dave Borowitz <dborowitz@google.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Dave Borowitz committed
Aug 19, 2015 at 11:26 UTC
f9e0952d1ff1c1f5c8fbbe9d914bb30012341a04
1 file changed
+3
-1
Documentation/git-push.txt
+3
-1
@@ -137,7 +137,9 @@ already exists on the remote side.
137
GPG-sign the push request to update refs on the receiving
138
side, to allow it to be checked by the hooks and/or be
139
logged. See linkgit:git-receive-pack[1] for the details
140
- on the receiving end.
140
+ on the receiving end. If the attempt to sign with `gpg` fails,
141
+ or if the server does not support signed pushes, the push will
142
+ fail.
143
144
--[no-]atomic::
145
Use an atomic transaction on the remote side if available.