lower minimum approver count on MR when merging between two protected branches
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Description
We have Gitflow projects where features are merged to develop, so we protect develop with a minimum approver count of 2. We also protect master with min. 2 reviewers as we don't want unreviewed code ending up in release tags.
Problem is now that this means that all code must now pass the review process twice. Once when it gets into develop and a second time when it trickles through to master.
This means that a developer has to bug his peers for bureaucratically clicking through the approvals that they already reviewed earlier. Especially for busy projects this consumes time and potentially leads to "review blindness".
Proposal
Add a project setting under "Merge request settings" that makes it possible to lower the minimum approver count for merge requests that merge from a protected branch to another protected branch. So, next to "Approvals required: ", add "Approvals required for merges between two protected branches: ".