Extend ProdOps triage-ops Processor
Overview
Following on from #3826 (closed) and gitlab-org/quality/triage-ops!1200 (merged), it would increase the efficiency of the ProdOps team if we could use triage-ops to perform a variety of actions on our behalf.
@brhea and @m_frankiewicz discussed next steps and decided that outlining a handful of use cases would be the best way forward in designing a "ProdOps bot."
Some conditions we would like to use in order to automate more of our work:
- apply labels to an MR when a given file is changed
- apply labels to an MR based on (lack of) activity
- update an MR milestone
- send a message to Slack when a given file is changed
Use cases
-
When an MR updates www-gitlab-com/.gitlab/merge_request_templates/Release-Post.md
apply the following labels: Product Operations, prodops:release, release post, templates - done with gitlab-org/quality/triage-ops!1280 (merged) -
When an issue with the Product Operations label hasn't had any activity for 60 days, mention @brhea
and@fseifoddini
in a comment with the following message, "🕗 Stale issue. Please review and decide on next steps." -
When an open issue or MR with the Product Operations label misses its milestone, update to current milestone (reference) -
When an MR merges with changes to www-gitlab-com/.gitlab/merge_request_templates/Release-Post.md
, send the following message to #release-post in Slack: "Release Post MR has been updated: #{MRTITLE}" -
On the 25th of the month, if the Issue titled "Release Post XX.Y Retrospective" is open (where XX.Y is the previous milestone), send the following message to the Slack channel #XX-Y-release-post-prep
: "Heads up! The Release Post XX.Y Retro is still open. Please finish the open tasks and close out the issue."