{"thread":{"id":"53304","subject":"Bad experience with gpg signing failures","startedAt":"2020-04-24T00:23:18Z","lastAt":"2020-04-24T00:23:18Z","messageCount":1,"participants":["Stan Pitucha"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"396077","messageId":"CAJ2_uEOk8xoLvK8B8PYc0_=kA8W_LqKwGyhKghemQDdRzA2nFA@mail.gmail.com","threadId":"53304","inReplyTo":null,"subject":"Bad experience with gpg signing failures","fromName":"Stan Pitucha","fromEmail":"stan.pitucha@envato.com","sentAt":"2020-04-24T00:23:02Z","receivedAt":"2020-04-24T00:23:18Z","isPatch":false,"sender":{"key":"stan.pitucha@envato.com","avatar":null},"body":"Hi all,\nThere are two issues I keep running into with gpg signing usability:\n\n1. When gpg fails to sign the commit, the error message is not\nforwarded. That means you always get \"gpg failed to sign the data\"\nwhen the actual gpg error is for example \"gpg: skipped ...: Unusable\nsecret key\". This makes the errors hard to deal with, because you\ndon't know which command actually failed without GIT_TRACE. That's\nespecially bad in case of transient errors.\n\n2. When gpg fails to sign the commit, it's not reported where it's\navailable. I found that it's possible to recover it from\nCOMMIT_EDITMSG from man pages, but it would be great if \"gpg failed to\nsign the data\" message was followed with \"your message draft was saved\nto .git/COMMIT_EDITMSG\" to make it more discoverable / not require\nreading full manual to find out about it.\n\n-- \nStan Pitucha\n\n\nSite Reliability Engineer at Envato\n\nhttp://envato.com\n\n\nThe email and any attachments are confidential and may contain\ninformation that is exempt from disclosure by law and subject to\ncopyright. If you have received this message in error please let me\nknow and delete it.\n"}]}