Skip to content

Add info on backend-complete label to Plan BE

John Hope requested to merge jh-backend-complete-label into master

Why is this change being made?

See https://gitlab.com/gitlab-org/plan/-/issues/277#note_558816401

Adds some short info on using the ~"Backend complete" label to communicate backend work having been merged and verified on an issue.

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 John Hope

Merge request reports