Updated bug triage document to highlight importance of using backport labels, and not add release labels manually (#33343)
This commit is contained in:
parent
c92dc98b90
commit
9657a3ac8b
1 changed files with 4 additions and 0 deletions
|
@ -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!
|
Loading…
Reference in a new issue