Showing results for 
Search instead for 
Did you mean: 
Copilot Lvl 2
Message 1 of 3

create branch protection rules at an organization level

I'm looking to see if there is a way to apply a default branch protection rule on master that is provided to all newly created repos. So let's say my organiztion is 




which has the repos






Is there a way to make a default protection for master that applies to any new repos I create, like





so that a rule would be created for master branch that requires an approved PR to commit to master and that approvals are automatically dismissed if a new upload to the branch becomes available, etc. Right now, we have a guide for my team on setting this up when they make a new repo, but we'd like something a bit more automatically enforced. Is there angle through the API I should investigate?

2 Replies
Community Manager
Message 2 of 3

Re: create branch protection rules at an organization level

Hi @grigjd3,


Thanks for reaching out! If you're a repository owner or have admin permissions in a repository, you can customize branch protections in the repository and enforce certain workflows per repo, perhaps CODEOWNERS could work here?

Thanks for being here, sharing, and keeping our community awesome!

Mark helpful posts with Accept as Solution to help other users locate important info. Don't forget to give Kudos for great content!

Copilot Lvl 2
Message 3 of 3

Re: create branch protection rules at an organization level

Thanks, I think either I'm misunderstanding CODEOWNERS or I am doing a bad job of communicating.  I realize I can add branch protections in a repo. What I'm trying to address is making sure that when my engineering team starts new projects (we do this fairly often), that we always have the same branch protections on master in each new project. If the person creating the new repo under our org has to manually set the branch protections each time, there are chances it won't get set correctly.  


It would be great if I could set a template branch protection for master that gets automagically applied to every new repo under our org. If the answer is that this functionality doesn't exist, I'll try to handle this through documentation or maybe through cloning a template repo, but it would be nice if this capability were built into github, given that github adds the concept of organizations on top of git.