Skip to content

Add initial Remote Development Workflow Triage

David O'Regan requested to merge master-patch-f85d into master

What does this MR do and why?

This MR does the following:

  • Add an initial rule for the groupide Remote Development Workflow
  • Removes our previous triage rules as they are not useful currently

Expected impact & dry-runs

These are strongly recommended to assist reviewers and reduce the time to merge your change.

See https://gitlab.com/gitlab-org/quality/triage-ops/-/tree/master/doc/scheduled#testing-policies-with-a-dry-run on how to perform dry-runs for new policies.

See https://gitlab.com/gitlab-org/quality/triage-ops/-/blob/master/doc/reactive/best_practices.md#use-the-sandbox-to-test-new-processors on how to make sure a new processor can be tested.

Done

Dry Run Output

https://gitlab.com/gitlab-org/quality/triage-ops/-/jobs/4390240207:

* Total after limiting: 2 resources
The following comments would be posted for the rule **Add  ~"rd-workflow::unprioritized" to any issue that has the ~"Category:Remote Development" label and does not have any existing "rd-workflow::*" labels**:
.[DEBUG] query_api: https://gitlab.com/api/v4/projects/278964/labels/rd-workflow%3A%3Aunprioritized?per_page=100
[DEBUG] rate_limit_infos: Rate limit remaining: 1998 (reset at 2023-06-01 06:55:57 +0000)

# https://gitlab.com/gitlab-org/gitlab/-/issues/413606
/label ~"rd-workflow::unprioritized"

# https://gitlab.com/gitlab-org/gitlab/-/issues/413587
/label ~"rd-workflow::unprioritized"

Confirmed with the board these are the correct issues:

Screenshot_2023-05-31_at_11.56.08_PM

Action items

  • (If applicable) Identify the affected groups and how to communicate to them:
    • /cc @person_or_group => oregand
    • Relevant Slack channels => g_create_ide
Edited by Chad Woolley

Merge request reports