Secure main branch: require PRs with owner approval, block direct pushes#25
Merged
Secure main branch: require PRs with owner approval, block direct pushes#25
Conversation
…anch Co-authored-by: leeoades <2321091+leeoades@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Update branch protection rules for main branch
Secure main branch: require PRs with owner approval, block direct pushes
Feb 19, 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.
Direct pushes to
mainare currently unrestricted. This adds branch protection enforced via GitHub API and code ownership to require all changes go through an approved PR.Changes
.github/CODEOWNERS@leeoadesas required reviewer for all files — every PR requires their explicit approval before merge.github/workflows/branch-protection.ymlmainviaactions/github-scriptusing the built-inGITHUB_TOKEN(administration: write)workflow_dispatch(trigger manually after merge) and on changes to the workflow file itselfRules enforced on
main:Feature branches are unaffected — force-push and delete remain unrestricted elsewhere.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.