DRAFT: [do not merge] Add one-off policy for pipeline-authoring group
One-off policy to migration open Issues/MRs to grouppipeline authoring
Dry Run Results
Issues
~"ci::*" label |
Count |
|---|---|
| ~"ci::persistence" | 38 |
| ~"ci::rules" | 130 |
| ~"ci::integrations" | 228 |
| ~"ci::bridge-pipelines" | 127 |
| ~"ci::dag" | 47 |
| ~"ci::authoring" | 461 |
Merge Requests
These numbers will change as MRs are opened/merged.
~"ci::*" label |
Count |
|---|---|
| ~"ci::persistence" | 0 |
| ~"ci::rules" | 1 |
| ~"ci::integrations" | 1 |
| ~"ci::bridge-pipelines" | 3 |
| ~"ci::dag" | 1 |
| ~"ci::authoring" | 3 |
Action items
-
(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 => -
Week-in-review
-
Edited by Kyle Wiebers