Cross-link the Approvals and Protected branches settings
This an actionable insight from the Code Review FY21-Q2 Category Maturity Scorecard research (insight).
What
There’s a disconnect between the MR Approvals and Protected branches settings, even though these features are very related. For example, to scope an approval rule by target branch, one needs to first set up a protected branch rule. Or, if one wants to require approvals by specific people (MR approvals) and approvals by Code Owners (Code owner approvals), they have to go to two separate places.
Why
In the MR approvals settings we have an information alert saying that Code Owner approvals moved to the Protected branches settings. But almost all of the participants didn’t read or completely dismissed that alert.
We should make it easier for users to jump between these settings to avoid confusion and improve feature discoverability.
How
While we work on a better placement for the MR approvals settings and on improving the organization of repository and MR policy settings, we can at least cross-link the Approvals and Protected branches settings, so that it’s easier to navigate back and forth between these very related features.