diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-12-12 21:07:46 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-12-12 21:07:46 +0300 |
| commit | 6121ad5af38294f12db08f13aec122c3dbef583a (patch) | |
| tree | 452bdd3003f26ad4cffb9005b176bb052b810a14 /doc/development/labels | |
| parent | 86a3b1b3ae2115c6ab7b9d492e9c89ac70963d3a (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/labels')
| -rw-r--r-- | doc/development/labels/index.md | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/development/labels/index.md b/doc/development/labels/index.md index 90253d101d4..4288408baf6 100644 --- a/doc/development/labels/index.md +++ b/doc/development/labels/index.md @@ -24,9 +24,9 @@ Most issues will have labels for at least one of the following: - Priority: `~"priority::1"`, `~"priority::2"`, `~"priority::3"`, `~"priority::4"` - Severity: `~"severity::1"`, `~"severity::2"`, `~"severity::3"`, `~"severity::4"` -Please add `~"breaking change"` label if the issue can be considered as a [breaking change](../deprecation_guidelines/index.md). +Add `~"breaking change"` label if the issue can be considered as a [breaking change](../deprecation_guidelines/index.md). -Please add `~security` label if the issue is related to application security. +Add `~security` label if the issue is related to application security. All labels, their meaning and priority are defined on the [labels page](https://gitlab.com/gitlab-org/gitlab/-/labels). @@ -252,7 +252,7 @@ We have the following priority labels: - `~"priority::3"` - `~"priority::4"` -Please refer to the issue triage [priority label](https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority) section in our handbook to see how it's used. +Refer to the issue triage [priority label](https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority) section in our handbook to see how it's used. ## Severity labels @@ -263,7 +263,7 @@ We have the following severity labels: - `~"severity::3"` - `~"severity::4"` -Please refer to the issue triage [severity label](https://about.gitlab.com/handbook/engineering/quality/issue-triage/#severity) section in our handbook to see how it's used. +Refer to the issue triage [severity label](https://about.gitlab.com/handbook/engineering/quality/issue-triage/#severity) section in our handbook to see how it's used. ## Label for community contributors @@ -301,7 +301,7 @@ with the [label `~"Community Challenge"`](https://gitlab.com/gitlab-org/gitlab/- If your MR for the `~"Community Challenge"` issue gets merged, you will also have a chance to win a custom GitLab merchandise. -If you've decided that you would like to work on an issue, please @-mention +If you've decided that you would like to work on an issue, @-mention the [appropriate product manager](https://about.gitlab.com/handbook/product/#who-to-talk-to-for-what) as soon as possible. The product manager will then pull in appropriate GitLab team members to further discuss scope, design, and technical considerations. This will |