Add a throughput labels rule to Danger
Problem to solve
Throughput labels are mandatory to set on merge requests. Also,
The Engineering Manager for each team is ultimately responsible for ensuring that these labels are set correctly, and should do this as a manual process on a schedule that is appropriate for their time.
This is a tedious manual work that never goes away. It can be scaled by having developers themselves setting these labels on MRs that don't inherit them from their respective issues (e.g. Documentation issues). In turn, it's always easy to forget doing this.
Permissions and Security
No extra permissions required. Danger tool that runs over GitLab CE/EE as a part of the CI pipeline should automatically pick up newly added Danger file and run it.
- Danger use in GitLab codebase: TBD
- Merge requests handbook page section to be updated with the notion of the new Danger check
- Merge requests page in docs to be updated with the notion of the new Danger check
Manual testing over a test branch of GitLab CE/EE is enough.
What does success look like, and how can we measure that?
Definition of success: all CE/EE merge requests have throughput labels assigned thus freeing EMs from doing that manually. Measure of success: number of MRs without throughput labels; it should radically decrease after adoption of this check.