Configure Protected Branches at the Group Level
Set Protected Branches at a Group Level
We have specific groups at Disney that have policies around their branching techniques. This would allow them to save ample time configuring each repo separately, which often results in hours spent.
- Why should someone use it; what's the underlying problem. the underlying problem is it takes hr of time to configure 100+ repos.
- What is the solution. Allow group admins to configure protected branches at a group level.
- How does someone use this? Allow toggles in the settings view to allow a configuration to apply to a repo.
During implementation, this can then be copied and used as a starter for the documentation.)