Harden repository governance - #118
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
Why
The interpreter and documentation are already well covered, but repository governance was not technically enforced and GitHub reported an incomplete community profile. These changes make workflow dependencies immutable, provide clear contribution paths, and document the project's security boundary and private reporting process.
Impact
There is no interpreter or CLI behavior change. Dependabot can continue updating GitHub Actions while their workflow references remain immutable.
Validation
git diff --check.github/**/*.ymlfile with Ruby's YAML parseruses:reference is a full commit SHASECURITY.mdas the single repository-wide policymake check(82.9% coverage, zero lint findings)make vuln(no vulnerabilities found)