Disable NewIssueWorkflowLabeller processor
requested to merge gitlab-community/quality/triage-ops:disable-new_issue_workflow_labeller into master
What does this MR do and why?
Whilst some details are being fleshed out we want to pause the new workflow labeller. See gitlab-org/developer-relations/contributor-success/team-task#382
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.
Action items
-
If adding environment variables for reactive processors, update config/triage-web.yamland.gitlab/ci/triage-web.yml -
(If applicable) Add documentation to the handbook pages for Triage Operations => -
(If applicable) Identify the affected groups and how to communicate to them: -
/cc @ person_or_group=> -
Relevant Slack channels => -
Engineering week-in-review
-