From 51c7afa95e58bc7f58c081509f046f9d49aa5041 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Domen=20Ko=C5=BEar?= Date: Tue, 25 May 2021 09:47:33 +0200 Subject: [PATCH] backport action: document the workflow --- doc/contributing/submitting-changes.chapter.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/doc/contributing/submitting-changes.chapter.md b/doc/contributing/submitting-changes.chapter.md index b462caf8670..0a465020092 100644 --- a/doc/contributing/submitting-changes.chapter.md +++ b/doc/contributing/submitting-changes.chapter.md @@ -248,6 +248,8 @@ For cherry-picking a commit to a stable release branch (“backporting”), use Add a reason for the backport by using `git cherry-pick -xe ` instead when it is not obvious from the original commit message. It is not needed when it's a minor version update that includes security and bug fixes but don't add new features or when the commit fixes an otherwise broken package. +For backporting Pull Requests to stable branches, assign label `backport ` to the original Pull Requests and automation should take care of the rest once the Pull Requests is merged. + Here is an example of a cherry-picked commit message with good reason description: ```