Draft: Add one-off migration to relabel group::organization to group::pods
What does this MR do and why?
This MR re-labels the epics, issues, and merge requests with ~"group::organization" to ~"group::pods", as well as updates the section and devops label assignments.
Target Label | Action |
---|---|
~group::organization | Remove label and assign to ~group::pods Change to ~section::enablement Change to ~devops::data_stores |
Related to #1267 (closed)
Expected impact & dry-runs
Relabel ~"group::organization" label to ~group::pods label, and add ~"section::enablement" and ~"devops::data_stores" labels in GitLab.org: https://gitlab.com/gitlab-org/quality/triage-ops/-/jobs/3906789047
-
✅ 142 epics, aligned with expectations. Epic list -
✅ 1991 issues, aligned with expectations. Issues list -
✅ 1036 merge requests, aligned with expectations. Merge requests list
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 Nao Hashizume