Skip to content

Commit ed93e45

Browse files
authored
Document triagebot label name constraint (#816)
1 parent cd74155 commit ed93e45

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

Diff for: src/release/issue-triaging.md

+9
Original file line numberDiff line numberDiff line change
@@ -145,6 +145,15 @@ There are many different labels that can be applied to issues.
145145
- An FCP will also cause a relnotes issue to be created, if it's started on an issue.
146146
- [`metabug`]: Tracks other bugs.
147147

148+
### Creating labels
149+
150+
<div class="warning">
151+
Triagebot needs to support `@rustbot label: xxx` usages terminated with a period or whitespace (as inline invocation), so the label name must consist of only alphanumeric or hyphen (`-`) or underscore (`_`) characters.
152+
</div>
153+
154+
- Check existing labels to make sure you're not duplicating them.
155+
- Discuss in <https://rust-lang.zulipchat.com/#narrow/channel/242269-t-release.2Ftriage/topic/New.20labels> if the new label may be non-conventional or controversial. Leave a comment about the new label as an FYI for others.
156+
148157
### Relnotes issues
149158

150159
Release note issues will currently come with `needs-triage` by default. The triage for relnotes is usually best done if you have sufficient context. Leave them as-is if you don't.

0 commit comments

Comments
 (0)