Skip to content

Create: Source Code - clarify that adding ~workflow::ready for development is not automatic

Nick Thomas requested to merge nick.thomas-master-patch-61519 into master

Why is this change being made?

Re-reading this process today, I noticed that the Label the issue as ~"workflow::ready for development" step of our planning process could be read as an automatic action to take. However, if the investigation reveals that we're not actually ready to work on a given issue, we shouldn't do this.

Very small clarifying change.

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
  • Assign this change to the correct DRI
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the "Maintained by" section in on the page being edited.
    • 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.
    • 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. (this requirement has been removed pending identification of a new DRI for the handbook)
Edited by Nick Thomas

Merge request reports