We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I think it would be valuable to sign extra packages and generate .asc files to allow offline checking (along a trusted key from repo?).
Is this desirable to automate this step? I think it will improve the chain of trust.
May an other action can do this..
According to current gh doc, gpg is only used for signing tags or commits
https://docs.github.com/en/authentication/managing-commit-signature-verification/generating-a-new-gpg-key
Relate-to: https://github.com/orgs/eclipse-csi/discussions/14#
This looks doable (but the trust could be a subject to debate)
https://github.com/yarnpkg/yarn/blob/master/.github/workflows/signing.yml
The text was updated successfully, but these errors were encountered:
Update signing.yml
2e76969
No branches or pull requests
I think it would be valuable to sign extra packages and generate .asc files to allow offline checking (along a trusted key from repo?).
Is this desirable to automate this step? I think it will improve the chain of trust.
May an other action can do this..
According to current gh doc, gpg is only used for signing tags or commits
https://docs.github.com/en/authentication/managing-commit-signature-verification/generating-a-new-gpg-key
Relate-to: https://github.com/orgs/eclipse-csi/discussions/14#
This looks doable (but the trust could be a subject to debate)
https://github.com/yarnpkg/yarn/blob/master/.github/workflows/signing.yml
The text was updated successfully, but these errors were encountered: