Branch Protection Rules at Organization level applying to all repos #16007
Replies: 17 comments 6 replies
-
Related to #13991. |
Beta Was this translation helpful? Give feedback.
-
This would be great to have for us too. |
Beta Was this translation helpful? Give feedback.
-
This might be of interest to people looking for such functionality and was recommended to us by our Github rep. We ended up implementing it for a 1000+ repos orgs and this work ok. Only issue is that the "dry-run" and the Cron based run take ~2 hours to run but the events based bits allow this to be a non-issue for now, just be sure that you implement it as two different Github App ( one for the reaction to events such as repos creation, branch protection modification, etc and another distinct one for events such as push and with the CRON env var ). Hope it help. |
Beta Was this translation helpful? Give feedback.
-
This is a feature that I would desperately want for my team. +1 to this. |
Beta Was this translation helpful? Give feedback.
-
+1 totally useful |
Beta Was this translation helpful? Give feedback.
-
+10000 all the agencies I've worked for would like this feature please |
Beta Was this translation helpful? Give feedback.
-
+1 very useful |
Beta Was this translation helpful? Give feedback.
-
Yes please! |
Beta Was this translation helpful? Give feedback.
-
+1 my customer looking for this functionality. |
Beta Was this translation helpful? Give feedback.
-
This is now supported as documented in Managing rulesets for repositories in your organization and Rulesets. 🥳 cc @sf-fingels |
Beta Was this translation helpful? Give feedback.
-
Can you please add a global protection rule (at least for master and main) and make it available also to GitHub Pro and GitHub Teams? This is always a security concern and it should be available to all paid plans |
Beta Was this translation helpful? Give feedback.
-
Another ➕ 1️⃣ |
Beta Was this translation helpful? Give feedback.
-
Yeah I would love to have this feature but no way am I going to quintuple my cost just to have it. Guys, this should be a standard paid feature for any plan, seriously. Even a small company can have dozens of repos for which they need standard rules. |
Beta Was this translation helpful? Give feedback.
-
I wrote a quick script to set all your preferred rules across your org's repos. You may need to adjust for your specific circumstances. See inline comments for config and guidance. Prereqs
Script
Just say NO to quintupling your github costs. |
Beta Was this translation helpful? Give feedback.
-
For teachers using GH Classroom this would be invaluable. I prefer my students to submit PR's and go through the real-world experience of having someone comment on a PR, etc. before merging. Allowing them to commit to main is just not something anyone would typically do on a group project. I don't even like having my master branch unprotected in my own projects. Please consider adding something like a default protection rule on a forked repo or something so students don't have to remember to create a rule for each of their assignments. |
Beta Was this translation helpful? Give feedback.
-
There are a number of open source projects on Github that aim to address this need: |
Beta Was this translation helpful? Give feedback.
-
There is a 50 post thread here requesting this since March 2019. Many +1s here.
The general idea is a desire to enforce a singular branch protection ruleset at an org level that would be applied to all repositories created within.
This removes the need to have each repo maintainer manually subscribe to rules on their own; which is prone to human error.
I would hope the the benefits related to security and ease of management would be self-evident. See the comments in the thread from many people who would greatly benefit from this feature.
Beta Was this translation helpful? Give feedback.
All reactions