summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMark Fletcher <mark@gitlab.com>2019-06-28 12:29:19 +0100
committerMark Fletcher <mark@gitlab.com>2019-06-28 12:29:23 +0100
commit8f506305e27928ef237686b4872a67ca2c948374 (patch)
tree85232c0c5481d36400fb2c1359b9cae8004b0276
parent046527beb585b8086e8b280dee78f43417b9a753 (diff)
downloadgitlab-ce-docs-update-subject-label-issue-workflow.tar.gz
Update issue workflow for subject labelsdocs-update-subject-label-issue-workflow
Mentions the automatic inference of stage and group labels based on the applied subject labels
-rw-r--r--doc/development/contributing/issue_workflow.md5
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/development/contributing/issue_workflow.md b/doc/development/contributing/issue_workflow.md
index 2f1ad5fa910..db426dec5e4 100644
--- a/doc/development/contributing/issue_workflow.md
+++ b/doc/development/contributing/issue_workflow.md
@@ -43,6 +43,10 @@ The descriptions on the [labels page][labels-page] explain what falls under each
Subject labels are labels that define what area or feature of GitLab this issue
hits. They are not always necessary, but very convenient.
+Subject labels are now used to infer and apply relevant group and devops stage
+labels. Please apply them whenever possible to facilitate accurate matching.
+Please refer to [this merge request][inferred-labels] for more information.
+
Examples of subject labels are ~wiki, ~ldap, ~api,
~issues, ~"merge requests", ~labels, and ~"Container Registry".
@@ -444,3 +448,4 @@ A recent example of this was the issue for
[labels-page]: https://gitlab.com/gitlab-org/gitlab-ce/labels
[ce-tracker]: https://gitlab.com/gitlab-org/gitlab-ce/issues
[ee-tracker]: https://gitlab.com/gitlab-org/gitlab-ee/issues
+[inferred-labels]: https://gitlab.com/gitlab-org/quality/triage-ops/merge_requests/155