File tree Expand file tree Collapse file tree 1 file changed +6
-6
lines changed Expand file tree Collapse file tree 1 file changed +6
-6
lines changed Original file line number Diff line number Diff line change @@ -376,10 +376,10 @@ Releases
376376
377377Backporting Fixes to the Release Branches
378378-----------------------------------------
379- You can use special comments on issues to make backport requests for the
380- release branches. This is done by making a comment containing the following
381- command on any issue that has been added to one of the "X.Y.Z Release"
382- milestones.
379+ You can use special comments on issues or pull requests to make backport
380+ requests for the release branches. This is done by making a comment containing
381+ the following command on any issue or pull request that has been added to one
382+ of the "X.Y.Z Release" milestones.
383383
384384::
385385
@@ -388,8 +388,8 @@ milestones.
388388This command takes one or more git commit hashes as arguments and will attempt
389389to cherry-pick the commit(s) to the release branch. If the commit(s) fail to
390390apply cleanly, then a comment with a link to the failing job will be added to
391- the issue. If the commit(s) do apply cleanly, then a pull request will
392- be created with the specified commits.
391+ the issue/pull request . If the commit(s) do apply cleanly, then a pull request
392+ will be created with the specified commits.
393393
394394If a commit you want to backport does not apply cleanly, you may resolve
395395the conflicts locally and then create a pull request against the release
You can’t perform that action at this time.
0 commit comments