GitHub Community
Set branch protection to "default" branches #22166
-
|
I know how to configure branch protection and about the new wildcards support, but is there a way always to define **master** and **develop** (for instance) as protected branches with the same rules? The wildcards pattern does not work in this case. I would work if it could support regular expression, but I know that’s not possible at the moment. We have many projects (and more coming), and they should all follow the same rules for these two main branches as soon as they are created on GitHub. Having to repeat the same steps every time is a bit frustrating. Also, some projects usually start with just **master** and the **develop** branch gets created only after the first release: project admins must remember to add this branch to the protected ones and trust me, it almost never happens before someone realises that the branch got commits “the wrong way”. |
Beta Was this translation helpful? Give feedback.
Replies: 8 comments
-
|
You may want to look at the Probot Settings app. It is specifically designed to make standardizing your configuration between repositories very easy, including branch protections. 🚨 WARNING 🚨 Note that this app inherently escalates anyone with |
Beta Was this translation helpful? Give feedback.
-
|
That looks interesting but also too dangerous. I think something native would prevent these permission issues and streamline the project’s configuration. The drawbacks of this suggestion would be too risky and I’m not sure why this should make the issue “Solved”. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @andreasciamanna, Thanks for this feedback! We’re always working to improve GitHub, and we consider every suggestion we receive. I’ve logged your feedback in our internal feature request list. Though I can’t guarantee anything or share a timeline for this, I can tell you that it’s been shared with the appropriate teams for consideration. Please let me know if you have any other questions. Cheers! |
Beta Was this translation helpful? Give feedback.
-
|
I have the exact same need. I’d like to globally protect the “master” branch of any repo within my organization so that it refuses direct push but requires PR instead. I can configure that manually for each repository, but that’s quite a waste of time. I’d also like to have that automated as I fork other OSS projects into my org. |
Beta Was this translation helpful? Give feedback.
-
|
Also really surprised there’s no way to specify default branch protection rules for the organization or account to apply to all new repos. This should definitely be a core feature. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah this seems to be a very core type feature that is missing and highly necessary in regulated industries or companies. I currently have a team that has to do this for every repo and it is pretty irritating. Consider another vote for this as an organizational level setting |
Beta Was this translation helpful? Give feedback.
-
|
Vadorequest:
This is exactly my usecase as well. I don’t want to have to add restrictions manually to each branch. Additionally, I’m worried that other team members who create repos might not remember to do this. |
Beta Was this translation helpful? Give feedback.
-
|
Roughly two years later.
I hope there will be a feature for this quite soon. 🙂 EDIT: This discussion, in my opinion, should be moved to Code Security. |
Beta Was this translation helpful? Give feedback.
You may want to look at the Probot Settings app. It is specifically designed to make standardizing your configuration between repositories very easy, including branch protections.
🚨 WARNING 🚨 Note that this app inherently escalates anyone with
pushpermissions to the admin role, since they can push config settings to themasterbranch, which will be synced. Use with caution.