Draft: Add group::knowledge one-off migration policy
What does this MR do and why?
Closes Change Group to Knowledge Group for Issues with... (#1263 - closed)
Apply the groupknowledge label to issues/MRs/Epics labeled with Category:Wiki , Category:Pages or Category:Content Editor
Note that @gitlab-bot will automatically apply the devopsplan so I will not include it to this migration policy.
Expected impact & dry-runs
Expected impact
Dry-run job
https://gitlab.com/gitlab-org/quality/triage-ops/-/jobs/3969364969
Impacted resources
Action items
-
If adding environment variables for reactive processors, update config/triage-web.yaml
and.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
-
Edited by Jennifer Li