diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2019-11-27 06:06:40 +0000 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2019-11-27 06:06:40 +0000 |
| commit | 688e33953d34ab8cd348d02ce79d8fdfe5353a03 (patch) | |
| tree | ee102361fc8a5bf5b2f4b05ca79ccef27b5c3102 /doc/development/contributing | |
| parent | 91f027ede40879af0bce406f2872e8d35c01e334 (diff) | |
| download | gitlab-ce-688e33953d34ab8cd348d02ce79d8fdfe5353a03.tar.gz | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/contributing')
| -rw-r--r-- | doc/development/contributing/issue_workflow.md | 24 |
1 files changed, 12 insertions, 12 deletions
diff --git a/doc/development/contributing/issue_workflow.md b/doc/development/contributing/issue_workflow.md index f32400d44a2..a385a7dc83a 100644 --- a/doc/development/contributing/issue_workflow.md +++ b/doc/development/contributing/issue_workflow.md @@ -40,17 +40,17 @@ scheduling into milestones. Labelling is a task for everyone. Most issues will have labels for at least one of the following: -- Type: ~feature, ~bug, ~backstage, etc. -- Stage: ~"devops::plan", ~"devops::create", etc. -- Group: ~"group::source code", ~"group::knowledge", ~"group::editor", etc. -- Category: ~"Category:Code Analytics", ~"Category:DevOps Score", ~"Category:Templates", etc. -- Feature: ~wiki, ~ldap, ~api, ~issues, ~"merge requests", etc. -- Department: ~UX, ~Quality -- Team: ~"Technical Writing", ~Delivery -- Specialization: ~frontend, ~backend, ~documentation -- Release Scoping: ~Deliverable, ~Stretch, ~"Next Patch Release" -- Priority: ~P1, ~P2, ~P3, ~P4 -- Severity: ~S1, ~S2, ~S3, ~S4 +- Type: `~feature`, `~bug`, `~backstage`, etc. +- Stage: `~"devops::plan"`, `~"devops::create"`, etc. +- Group: `~"group::source code"`, `~"group::knowledge"`, `~"group::editor"`, etc. +- Category: `~"Category:Code Analytics"`, `~"Category:DevOps Score"`, `~"Category:Templates"`, etc. +- Feature: `~wiki`, `~ldap`, `~api`, `~issues`, `~"merge requests"`, etc. +- Department: `~UX`, `~Quality` +- Team: `~"Technical Writing"`, `~Delivery` +- Specialization: `~frontend`, `~backend`, `~documentation` +- Release Scoping: `~Deliverable`, `~Stretch`, `~"Next Patch Release"` +- Priority: `~P1`, `~P2`, `~P3`, `~P4` +- Severity: ~`S1`, `~S2`, `~S3`, `~S4` All labels, their meaning and priority are defined on the [labels page](https://gitlab.com/gitlab-org/gitlab-foss/-/labels). @@ -210,7 +210,7 @@ If you are an expert in a particular area, it makes it easier to find issues to work on. You can also subscribe to those labels to receive an email each time an issue is labeled with a feature label corresponding to your expertise. -Examples of feature labels are ~wiki, ~ldap, ~api, ~issues, ~"merge requests" etc. +Examples of feature labels are `~wiki`, `~ldap`, `~api`, `~issues`, `~"merge requests"` etc. #### Naming and color convention |