diff options
| author | Mek Stittri <mstittri@gitlab.com> | 2019-06-28 22:28:16 +0000 |
|---|---|---|
| committer | Mek Stittri <mstittri@gitlab.com> | 2019-06-28 22:28:16 +0000 |
| commit | c74f6397266a84de72bfc6d6c1e27b6bac2356b0 (patch) | |
| tree | 74df34faf9edd5726e3bf8a3ebd5ba442e8d9ce3 | |
| parent | 3dcd8578c435cee572148a70b224cb80de8f36b9 (diff) | |
| download | gitlab-ce-clarify-team-group-stage-labels.tar.gz | |
Address Rémy's comment on Community Contributionclarify-team-group-stage-labels
| -rw-r--r-- | doc/development/contributing/issue_workflow.md | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/doc/development/contributing/issue_workflow.md b/doc/development/contributing/issue_workflow.md index af5ffb86633..7dc153b4602 100644 --- a/doc/development/contributing/issue_workflow.md +++ b/doc/development/contributing/issue_workflow.md @@ -30,8 +30,7 @@ labels, you can _always_ add the team and type, and often also the subject. Type labels are very important. They define what kind of issue this is. Every issue should have one or more. -Examples of type labels are ~feature, ~bug, ~backstage, ~security, -and ~"Community contribution". +Examples of type labels are ~feature, ~bug, ~backstage and ~security A number of type labels have a priority assigned to them, which automatically makes them float to the top, depending on their importance. |