aboutsummaryrefslogtreecommitdiffstats
path: root/docs/content/doc/usage/labels.en-us.md
diff options
context:
space:
mode:
authorBrecht Van Lommel <brecht@blender.org>2023-03-13 01:46:13 +0100
committerGitHub <noreply@github.com>2023-03-13 08:46:13 +0800
commita8e13e64da7f9dc6176365e6b9295981af5d81ea (patch)
treee087e6eb51ca0afd5c46ec257ddf7cfcf0661214 /docs/content/doc/usage/labels.en-us.md
parent43c136200a181858cf36a0a876cb6609aa804120 (diff)
downloadgitea-a8e13e64da7f9dc6176365e6b9295981af5d81ea.tar.gz
gitea-a8e13e64da7f9dc6176365e6b9295981af5d81ea.zip
Scoped label display and documentation tweaks (#23430)
* Fix scoped label left and right part breaking across lines. * Remove slanted divider in scoped label display, make it straight. After using this for a while, this feels more visually noisy than helpful. * Reduce contrast between scope and item to reduce probability of unreadable text on background. * Change documentation to remove mention of non-exclusive scoped labels. Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
Diffstat (limited to 'docs/content/doc/usage/labels.en-us.md')
-rw-r--r--docs/content/doc/usage/labels.en-us.md8
1 files changed, 3 insertions, 5 deletions
diff --git a/docs/content/doc/usage/labels.en-us.md b/docs/content/doc/usage/labels.en-us.md
index bf07c074ed..8e5ff1cf8d 100644
--- a/docs/content/doc/usage/labels.en-us.md
+++ b/docs/content/doc/usage/labels.en-us.md
@@ -23,17 +23,15 @@ For repositories, labels can be created by going to `Issues` and clicking on `La
For organizations, you can define organization-wide labels that are shared with all organization repositories, including both already-existing repositories as well as newly created ones. Organization-wide labels can be created in the organization `Settings`.
-Labels have a mandatory name, a mandatory color, an optional description, and must either be exclusive or not (see `Scoped labels` below).
+Labels have a mandatory name, a mandatory color, an optional description, and must either be exclusive or not (see `Scoped Labels` below).
When you create a repository, you can ensure certain labels exist by using the `Issue Labels` option. This option lists a number of available label sets that are [configured globally on your instance](../customizing-gitea/#labels). Its contained labels will all be created as well while creating the repository.
## Scoped Labels
-A scoped label is a label that contains `/` in its name (not at either end of the name). For example labels `kind/bug` and `kind/enhancement` both have scope `kind`. Such labels will display the scope with slightly darker color.
+Scoped labels are used to ensure at most a single label with the same scope is assigned to an issue or pull request. For example, if labels `kind/bug` and `kind/enhancement` have the Exclusive option set, an issue can only be classified as a bug or an enhancement.
-The scope of a label is determined based on the **last** `/`, so for example the scope of label `scope/subscope/item` is `scope/subscope`.
-
-Scoped labels can be marked as exclusive. This ensures at most a single label with the same scope is assigned to an issue or pull request. For example, if `kind/bug` and `kind/enhancement` are marked exclusive, an issue can only be classified as a bug or an enhancement.
+A scoped label must contain `/` in its name (not at either end of the name). The scope of a label is determined based on the **last** `/`, so for example the scope of label `scope/subscope/item` is `scope/subscope`.
## Filtering by Label