-
-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEAT] GPG Keys #3
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
Could you please expand on this, as Imagine the process is the same as on bare-metal. |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
I am still watching this, to facilitate any kind of automated ingestion of keys we need to understand the process that achieves this in the container and how to ingest the keys (IE should it be a mount, secret, env var? ) |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue is locked due to inactivity |
Is this a new feature request?
Wanted change
Github Desktop now offers the ability to use GPG keys to sign commits.
https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits
https://gist.github.com/xavierfoucrier/c156027fcc6ae23bcee1204199f177da
Would it be possible to have some way of easily importing GPG keys to be able to sign commits?
The request is purely "importing gpg keys to gpg in the container". The config can (and should) be done by the user.
E.g. A couple of ENV vars:
This then could run something like
gpg --import mykey1
gpg --import mykey2
Reason for change
Whilst it's doable in this image to implement the GPG key(s), the process is rather cumbersome.
Proposed code change
No response
The text was updated successfully, but these errors were encountered: