Add universal chainguard enforce commit signing config #156
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
xnox
force-pushed
the
chainguard-enforce-config-template
branch
2 times, most recently
from
d6004f7 to
f215810
Compare
This adds a universal chianguard enforce commit signing config. This supports all keyless and github verified signing methods, and covers all humans and trusted robots. Such config is universal, and will continue to work across repository renames and moves. If desired, the config can be locked down further but so far we haven't managed to make enforce a required check but hopefully such wide policy can actually be ratcheted to be made required as any and all signing methods are supported and trusted.
xnox
force-pushed
the
chainguard-enforce-config-template
branch
from
f215810 to
7fa5364
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds a universal chianguard enforce commit signing config. This
supports all keyless and github verified signing methods, and covers
all humans and trusted robots.
Such config is universal, and will continue to work across repository
renames and moves.
If desired, the config can be locked down further but so far we
haven't managed to make enforce a required check but hopefully such
wide policy can actually be ratcheted to be made required as any and
all signing methods are supported and trusted.