You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/release/issue-triaging.md
+9
Original file line number
Diff line number
Diff line change
@@ -145,6 +145,15 @@ There are many different labels that can be applied to issues.
145
145
- An FCP will also cause a relnotes issue to be created, if it's started on an issue.
146
146
-[`metabug`]: Tracks other bugs.
147
147
148
+
### Creating labels
149
+
150
+
<divclass="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
+
148
157
### Relnotes issues
149
158
150
159
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