2024-11-29 Untriaged community merge requests requiring initial triage

Hi merge request coaches,

Here is a list of the Community contribution merge requests that do not have a type, stage, nor group label. We would like to ask you to:

If missing, add a type label.
If missing, add a group label.
NOTE: Some group labels are not sufficient (e.g. groupdistribution), and you will need to use the lower level labels such as group::distributionbuild)
If missing, add a stage label.
Add relevant category labels to facilitate automatic addition of stage and group labels.
If no appropriate stage and group label, add a department or team label.
If an MR appears to be fixing a security vulnerability that you believe should not be public, please ask the AppSec team in the sec-appsec Slack channel.

Many times, using the quick action /copy_metadata <issue link> can fill in the necessary information. Please double-check to ensure the metadata is correct.

For the merge requests triaged please check off the box in front of the given merge request.

If the merge request is ready for review, assign a reviewer based on the following criteria:

If a group label is applied, assign a relevant reviewer from the product group. If none of the relevant reviewers have capacity, ping the engineering manager for the group.

If it's not clear who the relevant reviewers for this merge request are, assign a reviewer using reviewer roulette; the reviewer does not need to be an MR coach.

Once you've triaged all the merge requests assigned to you, you can unassign and unsubscribe yourself via these quick actions: