Skip to content

Update quad-planning to trigger off of `workflow::ready for development`

Justin Farris requested to merge justinfarris-updatequadplanning into master

Rather than creating more unique labels to track, we should leverage labels that are already being applied during development for more efficiency.

This MR updates the product development flow to trigger quad-planning off of the workflowready for development workflow state. The intent is to use the existing process PMs follow to drive more consistent engagement with SET prior to starting the development of a new feature.

Author Checklist

  • Provided a concise title for the MR
  • Added a description to this MR explaining the reasons for the proposed change, per [say-why-not-just-what][transparency]
  • Assign this change to the correct DRI
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to your manager.
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in [#mr-buddies][mr-buddies-slack].
    • If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files.
Edited by Farnoosh Seifoddini

Merge request reports