Repository navigation
docs: define repository ruleset requirements - #56
Merged
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Implements CLI-015 by documenting the exact intended GitHub repository ruleset for the
mainbranch and linking it from contributor guidance.Included
docs/contributing/repository-ruleset.mdmainRequired checks
The document requires only checks that currently exist and run on pull requests:
QualityCodeQLDependency Reviewis explicitly deferred until GitHub Dependency Graph is enabled, the workflow is merged, and a representative PR proves the check healthy. OpenSSF Scorecard is explicitly not a required PR check because it runs only in trusted main/scheduled contexts.Current repository state
The GitHub rulesets API currently returns no configured rulesets for this repository, so this PR documents the intended administrative configuration without falsely claiming enforcement already exists.
Security
Closes #18