From 276427d68558fa5dbd6bebba30590aa4d8530e24 Mon Sep 17 00:00:00 2001 From: Wayne Haber Date: Fri, 21 Aug 2020 12:43:04 +0000 Subject: Updated labeling recommendation based on community contributor experience --- doc/development/contributing/issue_workflow.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc/development/contributing/issue_workflow.md') 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: -- cgit v1.2.1