Suggest finding stable reviewer counterparts for multi-MR features
What does this MR do and why?
This MR adds a paragraph to the The responsibility of the merge request author section that suggests finding a set of reviewers/maintainers that will stay constant and will review all MRs for a feature. This applies where the author knows beforehand that the feature will consist of a larger number of MRs.
The motivation for this MR
Assume you created quick and dirty POC, and you know that you'll have many MRs for the same feature, then it's best to find a handful of reviewers (e.g. two frontend, two backend, ...), explain the context of the feature to them and send all MRs to them for a review.