You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
👋 Hello! I'm wondering if anyone has successfully gotten Spock working with GPG or knows of any workarounds besides disabling commit signing. Right now, commits don't work and I keep getting this error:
[2019-06-18 19:03:23] production.ERROR: Spock command exited unsuccessfully:
Command: git commit -m "Addon settings saved by admin"
Output: No output
Error:
error: cannot run gpg: No such file or directory
error: gpg failed to sign the data
fatal: failed to write commit object
Not a huge deal since I'm just on my local machine, but again, just putting this out there in case anyone has any insight.
Maybe it's worth adding the ability to specify some more Git configs within Spock's settings? What if you could arbitrarily add any config you wanted, and Spock would just add git -c key=value (in this case, git -c commit.gpgsign=false) to each commit? Is there anything inherently terrible in that approach?
The text was updated successfully, but these errors were encountered:
👋 Hello! I'm wondering if anyone has successfully gotten Spock working with GPG or knows of any workarounds besides disabling commit signing. Right now, commits don't work and I keep getting this error:
Not a huge deal since I'm just on my local machine, but again, just putting this out there in case anyone has any insight.
Maybe it's worth adding the ability to specify some more Git configs within Spock's settings? What if you could arbitrarily add any config you wanted, and Spock would just add
git -c key=value
(in this case,git -c commit.gpgsign=false
) to each commit? Is there anything inherently terrible in that approach?The text was updated successfully, but these errors were encountered: