Add a list of fresh Community contributions MRs to the "Stale merge requests" triage package
We currently have 314 team-tasks~2091545 MRs at https://gitlab.com/gitlab-org/gitlab-ce/merge_requests?label_name%5B%5D=Community+Contribution.
That's a lot and GitLab being an Open Source project, everyone should be involved in triaging and reviewing team-tasks~2091545 MRs.
Proposal
- Add a list of new Community contribution MRs to the "Stale merge requests" triage package (!41 (merged)).
- /cc the
@gitlab\-org/coaches
group on it
This depends on gitlab-org/gitlab-triage#112.
Old proposal
I propose to create an automated task that would assign all the opened team-tasks~2091545 that have no assignee and no comments to a random GitLab developer from the gl-coaches
group.
What would be asked of the developer is to triage the issue:
- add labels and milestone
- ping / assign the relevant people to have a look at it
Proposal by @markglenfletcher (#1 (comment 94643856)):
As @rymai mentioned we already have a rule for identifying ~"Community Contribution" MRs. Maybe the new rule could look something like this, to be applied after the labelling:
- name: Label community merge requests conditions: author_member: source: group condition: not_member_of source_id: gitlab-org labels: - No Label state: opened actions: labels: - Community Contribution - name: Assign community merge requests conditions: labels: - Community Contribution forbidden_labels: - auto-assigned assignee: Unassigned actions: assign: member_of: group: gitlab-org/gl-coaches labels: - auto-assigned comment: | Please label this MR label accordingly and ping/assign a relevant team member to review
This would also require
A new label for auto assignment (
auto-assigned
)Filtering on assignee:
gitlab-triage
feature for assignment of a random team member