Repository navigation
Link declared rulesets in project-administration from repository-setup.md - #465
Merged
hdamker merged 2 commits intoOct 7, 2026
Merged
Conversation
…ation instead of JSON copies
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.
What type of PR is this?
What this PR does / why we need it:
repository-setup.mdno longer carries JSON copies of the release rulesets. It links to the declared files in project-administration (config/rulesets/), points to the repository-config tool instead of the retiredapply-release-rulesets.sh, and addsrelease-tag-protectionto the ruleset description and the verification checklist.Which issue(s) this PR fixes:
Part of camaraproject/project-administration#310
Special notes for reviewers:
The links resolve once camaraproject/project-administration#311 is merged; merge this after it.
Changelog input
Additional documentation
This section can be blank.