Skip to content

Project repository settings inherit from Group

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Description

Large enterprise customers would like to control things like merge request settings and approvers across various business units or security concerns.

One example is for infrastructure as code projects, where different parts of the infrastructure are managed by different groups, and some groups are not allowed to make changes to parts of the infrastructure (security groups, VPCs).

It is very common for distinct teams to have their own requirements for branch protection, and approvals that need to be enforced on new projects within their group.

Proposal

Define Project repository settings at group level, and Project settings inherit from Group, especially for merge settings and approvers.

Links / references

Premium customer (priority for new implementation) - https://gitlab.my.salesforce.com/00161000004bZxf

@jramsay @mentat @MikeWalsh

Edited by 🤖 GitLab Bot 🤖