Set up a dedicated project for automated triage operations
We should create a project at gitlab-org/quality/triage-ops
that would be used for triaging all GitLab's projects. That would allow to reuse triage policies and centralize all the triaging efforts.
@meks said in Slack:
@godfat, I was just discussing with @rymai on how we can scale gitlab-triage processes. Instead of adding more complexity to the CE/EE yaml file, how about creating a sub project under
https://gitlab.com/gitlab-org/quality
. We can configure all the policy topics there as a dedicated pipeline. e.g.groom regressions
groom deliverables
mr coach
and etc. There may also be dependencies on these topics where we might want to run one before another, we can use the CI stages to configure this as well. What do you think ?
About the project path, @mlapierre said:
That might be confused with https://gitlab.com/gitlab-org/gitlab-triage. How about something like
triage-ops
? (edited)
and then
I only yesterday understood what
gitlab-triage
is, so havingquality/triage
as well would have made things harder. It would be fine for me now though, so maybe it's just a hurdle people will have to overcome?But I'd still prefer a name that conveys intent.