Bad experience with gpg signing failures

Bad experience with gpg signing failures

[Stan Pitucha]

Hi all,
There are two issues I keep running into with gpg signing usability:

1. When gpg fails to sign the commit, the error message is not
forwarded. That means you always get "gpg failed to sign the data"
when the actual gpg error is for example "gpg: skipped ...: Unusable
secret key". This makes the errors hard to deal with, because you
don't know which command actually failed without GIT_TRACE. That's
especially bad in case of transient errors.

2. When gpg fails to sign the commit, it's not reported where it's
available. I found that it's possible to recover it from
COMMIT_EDITMSG from man pages, but it would be great if "gpg failed to
sign the data" message was followed with "your message draft was saved
to .git/COMMIT_EDITMSG" to make it more discoverable / not require
reading full manual to find out about it.

-- 
Stan Pitucha


Site Reliability Engineer at Envato

http://envato.com


The email and any attachments are confidential and may contain
information that is exempt from disclosure by law and subject to
copyright. If you have received this message in error please let me
know and delete it.