Changes for content/handbook/engineering/infrastructure-platforms/developer-experience/workflow-automation.md: 2 added lines, 2 removed lines.
Original line number
Diff line number
Diff line
@@ -2,11 +2,11 @@
title:"WorkflowAutomation"
---
The Engineering Productivity team owns the tooling and processes for GitLab's internal workflow automation. [Triage-ops](https://gitlab.com/gitlab-org/quality/triage-ops) is one of the main projects the EP team maintains, which empowers GitLab team members to triage issues, MRs and epics automatically.
The Developer Experience stage owns the tooling and processes for GitLab's internal workflow automation. [Triage-ops](https://gitlab.com/gitlab-org/quality/triage-ops) is one of the main projects the Developer Experience stage maintains, which empowers GitLab team members to triage issues, MRs and epics automatically.
## One-off label migrations
In the event of team structure changes, we often need to run a one-off label migration to update labels on existing issues, MRs and epics. We encourage every team member to perform the migrations themselves for maximum efficiency. For the fastest result, please follow these instructions below to get started on a label migration merge request. The EP team can then help review and run the migrations if needed.
In the event of team structure changes, we often need to run a one-off label migration to update labels on existing issues, MRs and epics. We encourage every team member to perform the migrations themselves for maximum efficiency. For the fastest result, please follow these instructions below to get started on a label migration merge request. The Developer Experience stage can then help review and run the migrations if needed.
