foster/forgejo-docs
0
0
Fork 0
mirror of https://codeberg.org/forgejo/docs.git synced 2024-11-21 17:36:59 -05:00
Code Issues Activity

user/labels: rework the page entirely

Browse source
This commit is contained in:
Earl Warren 2023-10-23 12:18:12 +02:00
parent 64ba97d470
commit 88269f91ca
No known key found for this signature in database
GPG key ID: 0579CB2928A78A00
3 changed files with 13 additions and 11 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

BIN
docs/_images/user/labels/organization-labels-management.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 72 KiB

BIN
docs/_images/user/labels/repository-labels-management.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 51 KiB

24
docs/user/labels.md
View file

@ -6,21 +6,23 @@ origin_url: 'https://github.com/go-gitea/gitea/blob/abe8fe352711601fbcd24bf4505f
You can use labels to classify issues and pull requests and to improve your overview over them.
## Creating Labels
Labels can be created by going to the `Issues` page of a repository and clicking on `Labels` to show the labels management page.
For repositories, labels can be created by going to `Issues` and clicking on `Labels`.
![create a label](../_images/user/labels/label-new.png)
![repository labels management](../_images/user/labels/repository-labels-management.png)
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`.
![organization labels management](../_images/user/labels/organization-labels-management.png)
## Creating Labels
From the labels management page, click on the `New Label` button.
![create a label](../_images/user/labels/label-new.png)
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. Its contained labels will all be created as well while creating the repository.
![list of labels](../_images/user/labels/label-apply.png)
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. Its contained labels will all be created as well while creating the repository.
When you create a repository (or an organization), 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.
## Scoped Labels
@ -30,10 +32,10 @@ Scoped labels are used to ensure at most a single label with the same scope is a
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`.
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
Issue and pull request lists can be filtered by label. Selecting multiple labels shows issues and pull requests that have all selected labels assigned.
By holding alt to click the label, issues and pull requests with the chosen label are excluded from the list.
![list of labels](../_images/user/labels/label-apply.png)