Add GitHub Rulesets via .asf.yaml#705
Open
ppkarwasz wants to merge 2 commits into
Open
Conversation
Configure a minimal Ruleset to: - Prevent deletion and force-push on the default (`master`) branch and the `release` branch. - Prevent deletion, force-push, or update of any `rel/*` tag. Together, these rules satisfy the Tier 1 protection level defined by [Scorecard](https://github.com/ossf/scorecard/blob/main/docs/checks.md#branch-protection) and should allow for [SLSA Source L3](https://slsa.dev/spec/v1.2/source-requirements#source-l3) compliance, once we introduce a workflow to push provenance attestation at each commit.
Member
|
The branch called |
Member
Author
|
That was exactly something I meant to ask, but I forgot. It is fixed in 37cc35b |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Configure a minimal Ruleset to:
master) branch and thereleasebranch.rel/*tag.Together, these rules satisfy the Tier 1 protection level defined by Scorecard and should allow for SLSA Source L3 compliance, once we introduce a workflow to push provenance attestation at each commit.