Re-simplify managing merge request approvals.
Problem to solve
Managing approvers in a merge request became very cumbersome in GitLab Starter since v11.9. If there is value added in the new method it may be worth the cumbersomeness, but that ain't the case.
This issue is created in response to #1979 note 181414710.
since v11.9 | before v11.9 |
---|---|
|
|
|
|
|
|
Intended users
Developers creating merge requests.
Further details
Merge requests are an important, much used feature in GitLab.
Proposal
- Option 1: Detect GitLab Starter and use the (now removed) feature flag logic to show the old interface in Starter.
- Option 2: Add value in using the new method by enabling the new approval rules in GitLab Starter.
- Option 3: Revisit the approver selecting altogether and reduce the number of steps in all of EE.
Permissions and Security
This should not impact permissions or security.
Documentation
This page is subject to change: https://docs.gitlab.com/ee/user/project/merge_requests/merge_request_approvals.html
Testing
What does success look like, and how can we measure that?
What is the type of buyer?
GitLab EE Starter