about summary refs log tree commit diff
diff options
context:
space:
mode:
authorMatthias Krüger <matthias.krueger@famsik.de>2024-04-25 00:19:55 +0200
committerGitHub <noreply@github.com>2024-04-25 00:19:55 +0200
commit45beb36ef27aace1d44f929c9b5a56c1808b41ee (patch)
tree4df78affef44f5e0fe59acb4026820c7ca5c7445
parentf46b828b5536460b0fc1aeb8c08ddaddac684ffa (diff)
parent21906002ed01067d4257660696f92b205c72a882 (diff)
downloadrust-45beb36ef27aace1d44f929c9b5a56c1808b41ee.tar.gz
rust-45beb36ef27aace1d44f929c9b5a56c1808b41ee.zip
Rollup merge of #124334 - oli-obk:tracking-issue-policy, r=fmease
Strengthen tracking issue policy with consequences

As per the T-compiler MCP: https://github.com/rust-lang/compiler-team/issues/739
-rw-r--r--.github/ISSUE_TEMPLATE/tracking_issue.md2
1 files changed, 2 insertions, 0 deletions
diff --git a/.github/ISSUE_TEMPLATE/tracking_issue.md b/.github/ISSUE_TEMPLATE/tracking_issue.md
index 5f17f30b3b0..59862893611 100644
--- a/.github/ISSUE_TEMPLATE/tracking_issue.md
+++ b/.github/ISSUE_TEMPLATE/tracking_issue.md
@@ -28,6 +28,8 @@ Tracking issues are used to record the overall progress of implementation.
 They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
 A tracking issue is however *not* meant for large scale discussion, questions, or bug reports about a feature.
 Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
+Discussion comments will get marked as off-topic or deleted.
+Repeated discussions on the tracking issue may lead to the tracking issue getting locked.
 
 ### Steps
 <!--