Repository navigation
docs: require protection for release branches - #51
Merged
Merged
Conversation
lloydsmart
marked this pull request as ready for review
August 5, 2026 11:50
lloydsmart
force-pushed
the
docs/protect-main-during-backport
branch
from
August 5, 2026 11:51
bd4ca85 to
b08b74e
Compare
lloydsmart
changed the title
lloydsmart
marked this pull request as draft
August 5, 2026 11:52
lloydsmart
marked this pull request as ready for review
August 5, 2026 11:53
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
mainanddevelopmust be protected against deletion and force pushesmain→developrelease backport workflowThe corresponding minimal branch-protection rules have now been enabled for both branches, including administrator enforcement.
Validation
npx --yes markdownlint-cli2 RELEASING.mdgit diff --check