summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorWayne Haber <whaber@gitlab.com>2020-08-21 12:43:04 +0000
committerWayne Haber <whaber@gitlab.com>2020-08-21 12:43:04 +0000
commit276427d68558fa5dbd6bebba30590aa4d8530e24 (patch)
tree209b132b9a6c090052b1d869443482199b7ee986
parent4ea7a80898d3266d386ca928d7c253d4bf588e1c (diff)
downloadgitlab-ce-whaber-77.tar.gz
Updated labeling recommendation based on community contributor experiencewhaber-77
-rw-r--r--doc/development/contributing/issue_workflow.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/contributing/issue_workflow.md b/doc/development/contributing/issue_workflow.md
index ea24e216d58..cf8448cca13 100644
--- a/doc/development/contributing/issue_workflow.md
+++ b/doc/development/contributing/issue_workflow.md
@@ -36,7 +36,7 @@ project.
To allow for asynchronous issue handling, we use [milestones](https://gitlab.com/groups/gitlab-org/-/milestones)
and [labels](https://gitlab.com/gitlab-org/gitlab/-/labels). Leads and product managers handle most of the
-scheduling into milestones. Labeling is a task for everyone.
+scheduling into milestones. Labeling is a task for everyone (however for some projects labels can only be set by GitLab team members and cannot be set by community contributors).
Most issues will have labels for at least one of the following: