Add workflow::ready for design to forbidden_labels
What does this MR do and why?
This MR adds workflowready for design to forbidden_labels
, as this label signals the issue is still not ready for development.
- See this Slack thread in
#development
(internal, good for 90 days). - Handbook description of the label: https://about.gitlab.com/handbook/product-development-flow/#outcomes-and-activities-2.
Expected impact & dry-runs
These are strongly recommended to assist reviewers and reduce the time to merge your change.
See https://gitlab.com/gitlab-org/quality/triage-ops/-/tree/master/doc/scheduled#testing-with-a-dry-run on how to perform dry-runs.
Action items
-
(If applicable) Add documentation to the handbook pages for Triage Operations => gitlab-com/www-gitlab-com!109226 (merged) (will be reviewed once this change merges) - (If applicable) Identify the affected groups and how to communicate to them:
-
/cc @ person_or_group
=> -
Relevant Slack channels => -
Engineering week-in-review
-
Edited by Luke Duncalfe