-
Notifications
You must be signed in to change notification settings - Fork 43
gpg: signing failed: No secret key #72
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
Is this the reason #50 (comment)? If so, any plans on how to solve this? |
@brazarb we're you able to sign off commits, i am using a similar approach to yours and keep getting the same error |
@brazarb you can give this a look, it was of help |
Also running into this issue. It appears to be because the commitizen action is run in a Docker image using a different version of gpg and in-container configuration path, whereas |
I've followed the steps using crazy-max/ghaction-import-gpg as the documentation recommended.
However I'm having no luck getting the commitizen-action to sign the commits/tags etc.
Checking
git config --global --list
matches the name, email and signing key.The text was updated successfully, but these errors were encountered: