docs: back up branch protection ruleset configuration - #16
Merged
Conversation
Adds .github/rulesets/README.md and branches/{default-branch,releases}.json,
documenting the two rulesets already active on this repo. Matches the
standard tracking pattern used across the org; this repo had the live
rulesets but never got the backup files.
The documented template was missing the synchronize/edited trigger types and the explicit issues/pull-requests write permissions block that every repo in the org actually has. Discovered while bringing tool-bpf, packrat, and others into compliance with this skill's documented standard -- the live repos were right, the doc was stale.
atheurer
approved these changes
Aug 5, 2026
atheurer
left a comment
atheurer
left a comment
There was a problem hiding this comment.
Ruleset backups match the standard pattern already verified in tool-bpf/tool-power. The SKILL.md fork-check.yaml template fix (adding synchronize/edited triggers + issues/pull-requests permissions) brings it in line with the actual deployed workflow I verified byte-for-byte in packrat, tool-power, and tool-sysstat. LGTM.
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.
Summary
.github/rulesets/README.mdand.github/rulesets/branches/{default-branch,releases}.json, backing up the two rulesets already active on this repo (fetched live from the GitHub API, metadata stripped)new-reposkill'sfork-check.yamltemplate, which was missing thesynchronize/editedtrigger types and theissues/pull-requestswritepermissions:block that every actual repo in the org hasFound during an org-wide audit of standard repo files/protections: live rulesets and team permissions were already correctly configured here, but the backup/documentation files were never committed. While fixing that gap in other repos (tool-bpf, packrat), found the skill's own template was stale compared to what's actually deployed everywhere.
Note:
fork-check.yamlis intentionally not being added to this repo in this PR — its only workflow (run-crucible-tracking) doesn't consume org secrets or run untrusted PR content, so the fork-check guard doesn't apply here.🤖 Generated with Claude Code