feat: protect maintenance branches - #26
Merged
Merged
Conversation
|
🎉 This PR is included in version 1.2.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This was referenced Aug 7, 2026
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
content/1.x(refs/heads/1.x) from deletion and non-fast-forward updates and require linear history plus pull requestsConventional PR titlecheck on1.xwithout prematurely requiringContent validationSafe staged CI policy
The live
content/1.xbranch was verified at01b1fdb65c2243df4bafe9c8109fc93229df0121.pull_request_targetalready emitsConventional PR titlewithout a base-branch filter. The content validation workflow currently targets onlymain, so requiringContent validationnow would deadlock maintenance pull requests. A follow-up content workflow change must enable and prove that check on1.x, then add it to this entry before applying the tighter policy.Fresh replacement repositories remain absent from
required_ci.Validation
bin/validatebash -n bin/publish bin/publish-repositories bin/validate tests/publish-maintenance-branch.shshellcheck bin/publish bin/publish-repositories bin/validate tests/publish-maintenance-branch.shtests/publish-maintenance-branch.shactionlintgit diff --checkbin/publishagainst the live Team organization in plan modeThe live plan contains one new organization-ruleset
POST, no ruleset deletion, and no settings apply. Local fake-API apply tests inspect the generated payload for both policy scopes and confirm the exact branch, repository, rule types, GitHub Actions integration ID, stale-rule cleanup, and absence of fresh-repository CI rules.Review and rollback
Do not run
bin/publish --applyuntil this pull request is merged and separately authorized. To roll back after a future apply, remove the maintenance entry, merge that reviewed change, and confirm the plan deletes only05 - Maintenance branch - content - 1.xbefore applying.Manual verification
No runtime topology applies to organization policy. From this branch run: