summaryrefslogtreecommitdiff
path: root/t/t4018/golang-long-func
diff options
context:
space:
mode:
authorLibravatar Han Xin <hanxin.hx@alibaba-inc.com>2020-09-19 22:47:50 +0800
committerLibravatar Junio C Hamano <gitster@pobox.com>2020-09-19 15:56:39 -0700
commita4f324a423ddfe3680bf6105f8c113d0e76305a0 (patch)
tree9b899646ae12f4e0457eb78852cf69dd7f870f48 /t/t4018/golang-long-func
parentFourteenth batch (diff)
downloadtgif-a4f324a423ddfe3680bf6105f8c113d0e76305a0.tar.xz
send-pack: run GPG after atomic push checking
The refs update commands can be sent to the server side in two different ways: GPG-signed or unsigned. We should run these two operations in the same "Finally, tell the other end!" code block, but they are seperated by the "Clear the status for each ref" code block. This will result in a slight performance loss, because the failed atomic push will still perform unnecessary preparations for shallow advertise and GPG-signed commands buffers, and user may have to be bothered by the (possible) GPG passphrase input when there is nothing to sign. Add a new test case to t5534 to ensure GPG will not be called when the GPG-signed atomic push fails. Signed-off-by: Han Xin <hanxin.hx@alibaba-inc.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t4018/golang-long-func')
0 files changed, 0 insertions, 0 deletions