Skip to content

Automate adding label "development guidelines"

Summary

If a merge request contains changes to any file inside doc/development, could we please auto-apply the development guidelines label to it? It will help the Technical Writing team track how many merge requests we work for developer docs.

Project: https://gitlab.com/gitlab-org/

I'm not sure what to select from this list, so I'm leaving it blank:

  • Automation that does not require an assignee.
    • Rescheduling of milestones (milestone refinement)
    • Labelling missed-deliverable and missed:x.y based on the scheduled milestone.
    • Labelling ~"bug" on regression and on regression:x.y.
    • Labelling priority1 and severity1 on master:broken.
    • Labelling SLOMissed on issues with ~"bug" past SLO priority target.
    • Discovery of potential and popular proposals.
    • Remind people to add labels if an issue has no labels.
  • Triage reports
    • Untriaged issue triage reports, please list assignee: ASSIGNEE_NEEDED
    • Community Merge Requests, please list coaches: COACHES_LIST
    • Group triage reports
  • WIP: Infer stage and group labels from subject labels