2024-08-16 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:

1. If missing, add a type label.
2. If missing, add a group label.
   NOTE: Some group labels are not sufficient (e.g. groupdistribution or groupgitaly and you will need to use the lower level labels such as group::gitalycluster)
3. If missing, add a stage label.
4. Add relevant category labels to facilitate automatic addition of stage and group labels.
5. If no appropriate stage and group label, add a department or team label.
6. 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:

/done
/unassign me
/unsubscribe

Alternatively, you can use the existing project comment template or create a custom one with the above quick actions.

When all the checkboxes are done, close the issue, and celebrate!

@nao.hashizume

• Disable PostgreSQL on GitLab Rails nodes in ref... (gitlab-org/gitlab!162812 - closed) (by @bbodenmiller) - Community contribution, Leading Organization, docs-only, docsimprovement, documentation, maintenancerefactor, twtriaged, typemaintenance, workflowready for review

@oksanakohuch-ext

• Omit extra nginx enablement in ref arch (gitlab-org/gitlab!162811 - merged) (by @bbodenmiller) - Community contribution, Leading Organization, docs-only, docsimprovement, documentation, maintenancerefactor, twtriaged, typemaintenance, workflowready for review

@pslaughter

• invalid redirect_uri fix (gitlab-org/gitlab!162821 - merged) (by @ikrmaahmad47) - 1st contribution, Community contribution, devopsgovern, docs-only, documentation, groupauthentication, sectionsec, twtriaged, workflowready for review

@reprazent

• Allow pull_policy to be unset when defining all... (gitlab-org/gitlab-runner!4943 - merged) (by @magicmayo) - 1st contribution, Category:Runner Core, Community contribution, devopsverify, grouprunner, linked-issue, sectionci, workflowin dev

@splattael

• Disable Redis on GitLab Rails nodes in ref arch (gitlab-org/gitlab!162810 - closed) (by @bbodenmiller) - Community contribution, Leading Organization, docs-only, docsimprovement, documentation, maintenancerefactor, twtriaged, typemaintenance, workflowready for review

@terrichu

• Improve Some Markdown Image Alt Tags (gitlab-org/gitlab!162767 - merged) (by @Jitsusama) - 1st contribution, Community contribution, Technical Writing, docs-only, documentation, linked-issue, twtriaged, workflowready for review

---

Job URL: https://gitlab.com/gitlab-org/quality/triage-ops/-/jobs/7596639714

This report was generated from this policy