Create a report for idle team merge requests
When creating or changing a new triage policy or triage package:
-
Consider adding documentation to the handbook pages for Triage Operations: gitlab-com/www-gitlab-com!48764 (merged) -
Consider announcing to the appropriate Slack channels or week-in-review - #late_merge_request_analysis and also shared in #development
-
week-in-review
TODO
-
Only assign to engineering managers -> #470 (closed) -
Figure out how to run this every 2 weeksWe run this on 8th and 23rd -
Add some tests -
Add documentation - Handbook: gitlab-com/www-gitlab-com!48764 (merged), gitlab-com/www-gitlab-com!49949 (merged), gitlab-com/www-gitlab-com!50359 (merged)
- How we generate the policy files, and CI jobs
Latest dry-run schedule:
https://gitlab.com/gitlab-org/quality/triage-ops/pipelines/141566742https://gitlab.com/gitlab-org/quality/triage-ops/pipelines/146153575- https://gitlab.com/gitlab-org/quality/triage-ops/pipelines/146499090
Dry-runs:
These counts are not mutually exclusive (4 week MRs are included in 2 week MRs)
Closes #453 (closed)
Edited by Lin Jen-Shin