Manage repository settings as code alongside the ruleset - #1
Merged
Conversation
lorisleiva
added a commit
to codama-idl/spec
that referenced
this pull request
Aug 28, 2026
This PR updates RELEASING.md for codama-idl/release-tools#1: the sync workflow is now called `sync-policies` and applies both the branch-protection ruleset and the canonical repository settings (`repo-settings.json`).
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
1 participant
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.
This PR generalises the policy sync from branch protection only to full repository policy:
repo-settings.json: the canonical repository settings applied viaPATCH /repos/{org}/{repo}— squash-only merges, the trailer-preserving "Default message" squash defaults (COMMIT_OR_PR_TITLE+COMMIT_MESSAGES, which keepcherry-pick -xtrailers greppable for the promote-time audit), auto-merge, and delete-branch-on-merge. This codifies the settings sweep previously done by hand in the UI and self-heals any drift on every sync.sync-rulesetsbecomessync-policies: one dispatch applies the settings and upserts the ruleset per repository, with a two-column summary table.ruleset.jsonnow restricts protected-branch merges tosquashas belt-and-braces on top of the repo settings.After merging, dispatch Sync policies to roll it out (expected: settings applied ×12, ruleset updated ×12, including this repository's own settings).