Improve the reviewer assignment process for community contributions
Summary
The process for a community contributions to get a reviewer assigned is convoluted and inefficient.
Example - gitlab-org/gitlab!81972 (comment 865120579)
- First the bot asks for a danger token - gitlab-org/gitlab!81972 (comment 859566931)
- Danger runs and suggests a reviewer via review roulette - gitlab-org/gitlab!81972 (comment 859613619)
- The community contributor then has to manually ask for review - gitlab-org/gitlab!81972 (comment 859683329) and gitlab-org/gitlab!81972 (comment 865120579)
Proposal
-
Iteration 1: Allow to specify people for review => !1407 (merged) -
Iteration 2: Replace MR coach ping with relevant team member ping based on the group label (and speciality), and fallback to MR coach => !1454 (merged)
Edited by Rémy Coutable