Costly To Enforce Repository-Level Feature Across An Entire Group
Problem to solve
Enforcing the use of repository-level features across all repositories within groups, and sub-groups, of a top-level group.
I would like to enable the
Committer restriction option on all my existing repositories within the
hyper-expanse group, along with all newly created repositories in the future.
The particular feature itself is inconsequential (Different groups will want, or need, to enforce different sets of rules. Mozilla published a post about the importance of enforcing a set of security best practices across all of their repositories.)
However, there's a non-zero cost to rolling out that feature to all my exiting repositories, and ensuring that the feature is enabled on all future repositories.
What does success look like, and how can we measure that?
Cost of enabling a repository-level feature should remain constant regardless of the number of existing repositories or newly created repositories.