mirror of
https://codeberg.org/forgejo/docs.git
synced 2024-11-21 17:36:59 -05:00
add labels user documentation
This commit is contained in:
parent
fdbba10aa5
commit
adbfcac8d9
5 changed files with 39 additions and 0 deletions
BIN
v1.19/_images/user/labels/label-apply.png
Normal file
BIN
v1.19/_images/user/labels/label-apply.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 24 KiB |
BIN
v1.19/_images/user/labels/label-list.png
Normal file
BIN
v1.19/_images/user/labels/label-list.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 35 KiB |
BIN
v1.19/_images/user/labels/label-new.png
Normal file
BIN
v1.19/_images/user/labels/label-new.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 21 KiB |
|
@ -9,6 +9,7 @@ involved in running it on their machines.
|
|||
- [Your First Repository](first-repository)
|
||||
- [Branch and tag protection](protection)
|
||||
- [Projects / Kanban boards](project)
|
||||
- [Labels](labels)
|
||||
- [Webhooks](webhooks)
|
||||
- Authentication
|
||||
- [LDAP, PAM, FreeIPA](authentication)
|
||||
|
|
38
v1.19/user/labels.md
Normal file
38
v1.19/user/labels.md
Normal file
|
@ -0,0 +1,38 @@
|
|||
---
|
||||
layout: '~/layouts/Markdown.astro'
|
||||
title: 'Labels'
|
||||
license: 'Apache-2.0'
|
||||
origin_url: 'https://github.com/go-gitea/gitea/blob/5d621fe9a7f27b5168db22dc38423b71037bcae0/docs/content/doc/usage/labels.en-us.md'
|
||||
---
|
||||
|
||||
You can use labels to classify issues and pull requests and to improve your overview over them.
|
||||
|
||||
## Creating Labels
|
||||
|
||||
For repositories, labels can be created by going to `Issues` and clicking on `Labels`.
|
||||
|
||||
![create a label](../../../../images/v1.19/user/labels/label-new.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`.
|
||||
|
||||
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/v1.19/user/labels/label-apply.png)
|
||||
|
||||
## 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.
|
||||
|
||||
![list of labels](../../../../images/v1.19/user/labels/label-list.png)
|
||||
|
||||
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.
|
||||
|
||||
## 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.
|
Loading…
Reference in a new issue