From 7d135f4dad34fa288f3233063a24535da03cd283 Mon Sep 17 00:00:00 2001 From: Kevin Parsons Date: Thu, 19 Nov 2020 12:00:37 -0800 Subject: [PATCH] Update backports documentation Signed-off-by: Kevin Parsons --- RELEASES.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/RELEASES.md b/RELEASES.md index 0ea49e1ef422..469a19a1c24f 100644 --- a/RELEASES.md +++ b/RELEASES.md @@ -134,7 +134,7 @@ To cherry pick a straightforward commit from master, simply use the cherry pick process: 1. Pick the branch to which you want backported, usually in the format - `release/.`. The following will create a branch you can + `release/.`. The following will create a branch you can use to open a PR: ```console @@ -155,7 +155,12 @@ process: Make sure to replace `stevvooe` with whatever fork you are using to open the PR. When you open the PR, make sure to switch `master` with whatever - release branch you are targeting with the fix. + release branch you are targeting with the fix. Make sure the PR title has + `[]` prefixed. e.g.: + + ``` + [release/1.4] Fix foo in bar + ``` If there is no existing fix in master, you should first fix the bug in master, or ask us a maintainer or contributor to do it via an issue. Once that PR is