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
376
376
377
377
Backporting Fixes to the Release Branches
378
378
-----------------------------------------
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.
383
383
384
384
::
385
385
@@ -388,8 +388,8 @@ milestones.
388
388
This command takes one or more git commit hashes as arguments and will attempt
389
389
to cherry-pick the commit(s) to the release branch. If the commit(s) fail to
390
390
apply 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.
393
393
394
394
If a commit you want to backport does not apply cleanly, you may resolve
395
395
the conflicts locally and then create a pull request against the release
You can’t perform that action at this time.
0 commit comments