Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add basic documentation for labels, including scoped labels #23304

Merged
merged 4 commits into from
Mar 5, 2023
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update docs/content/doc/usage/labels.en-us.md
Co-authored-by: delvh <dev.lh@web.de>
  • Loading branch information
brechtvl and delvh committed Mar 4, 2023
commit 56e6f03f35b4b94a9f5961c8798df9e9fd47a0cd
4 changes: 2 additions & 2 deletions docs/content/doc/usage/labels.en-us.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,9 +32,9 @@ Its contained labels will all be created as well while creating the repo.
## Scoped Labels

You can decrease your error susceptibility by using scoped labels. \
A scoped label is a label containing `/` in its name (not at either end of the name) and marking the label as `exclusive`. \
A scoped label is a label that is marked as `exclusive` and contains `/` in its name (not at either end of the name). \
For example, if label `A` is called `scope/item`, label `B` is called `scope/second-item`, and both are marked as `exclusive`, an issue cannot be labeled with both `A` and `B` at the same time. \
Such an issue can have at most one of these labels, or none. \
Issues can have at most one of these labels per scope, or none. \
The scope of a label is determined based on the **last** `/`, so for example the scope of label `subscope/subscope2/item` would be `subscope/subscope2`.

## Filtering by Label
Expand Down