From 9657a3ac8bb1e1fe1335363d23c55d4a3cf9de6d Mon Sep 17 00:00:00 2001
From: Stian Thorgersen <stianst@gmail.com>
Date: Fri, 27 Sep 2024 13:58:04 +0200
Subject: [PATCH] Updated bug triage document to highlight importance of using
 backport labels, and not add release labels manually (#33343)

---
 docs/bug-triage.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/docs/bug-triage.md b/docs/bug-triage.md
index d68829847e..39b09c0fa1 100644
--- a/docs/bug-triage.md
+++ b/docs/bug-triage.md
@@ -97,3 +97,7 @@ When triaging or fixing an issue consider if the fix should be backported. If it
 corresponding `backport/<release branch>` label.
 
 For convenience, use the `.github/scripts/pr-backport.sh` to help create the backport PRs. 
+
+By adding a `backport/<release branch>` label to the issue it is automatically added to the patch release project, and
+additionally when merging the PR the `backport/<release branch>` is automatically replaced with a `release/x.y.z` label.
+Please do not add `release/x.y.z` manually!  
\ No newline at end of file