From f521791123847e76bace07ed67fb621fe00fff50 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=E8=AE=B8=E6=9D=B0=E5=8F=8B=20Jieyou=20Xu=20=28Joe=29?=
 <39484203+jieyouxu@users.noreply.github.com>
Date: Thu, 6 Mar 2025 00:43:19 +0800
Subject: [PATCH] Document triagebot label name constraint

---
 src/release/issue-triaging.md | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/src/release/issue-triaging.md b/src/release/issue-triaging.md
index 56e925d5b..70cd4671f 100644
--- a/src/release/issue-triaging.md
+++ b/src/release/issue-triaging.md
@@ -145,6 +145,15 @@ There are many different labels that can be applied to issues.
   - An FCP will also cause a relnotes issue to be created, if it's started on an issue.
 - [`metabug`]: Tracks other bugs.
 
+### Creating labels
+
+<div class="warning">
+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.
+</div>
+
+- Check existing labels to make sure you're not duplicating them.
+- 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.
+
 ### Relnotes issues
 
 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.