Merge request approval gaps
Whilst we appreciate merge request approvals are working for some organisations, the current model doesn’t quite fit our process. Our current (manual) process is we require one code review and one functional review. These need to be distinct i.e. the same person cannot approve both the functionality and code. We are currently reviewing the Gitlab EE offering to see if it covers all of our requirements. We believe it is almost there, but have a few questions/gaps.
Specific rule approvals
With the current implementation it appears if someone is able to approve multiple rules, they can’t approve a specific rule. Is this correct or is there a way to specify which rule(s) you are approving? We would like to be have a button added by each rule so that it’s possible to choose which rule you wish to approve.
Distinct approvers
Having the ability to approve a specific rule is a precursor to this requirement. Assuming that this is not possible already, we would like a configuration option to prevent the same approver from approving multiple rules.
Approval rules setup
It appears that approval rules are configured at project level. Is there any way to set the approval rules at instance level or group level?