Skip to content

Commit 21ece11

Browse files
Merge pull request #399 from fultonj/cherry-robot
Document using openshift-cherrypick-robot Reviewed-by: Andrew Bays <[email protected]> Reviewed-by: John Fulton <[email protected]>
2 parents e6df7fd + a199985 commit 21ece11

File tree

1 file changed

+19
-1
lines changed

1 file changed

+19
-1
lines changed

docs/contributing/cherry-picking.md

+19-1
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,25 @@ cherry pick.
1414

1515
Please do not ask [core maintainers](../../OWNERS) to cherry pick your
1616
patch though we will be happy to review it and help merge it once the
17-
cherry pick PR has been submitted.
17+
cherry pick PR has been submitted using one of the methods below.
18+
19+
## Method 1
20+
21+
Add a comment like the following to the PR you wish to cherry pick.
22+
```
23+
/cherrypick 18.0.0-proposed
24+
```
25+
The [openshift-cherrypick-robot](https://github.com/openshift-cherrypick-robot)
26+
will then attempt to create a new PR of the original PR (after it
27+
merges) with a cherry-pick of the same patch into the desired branch.
28+
There are
29+
[examples](https://github.com/openstack-k8s-operators/architecture/pull/395#issuecomment-2352668300)
30+
of this in previous PRs in this repository.
31+
32+
If there is a [merge conflict](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line),
33+
then method 1 will not work and you will need to use method 2.
34+
35+
## Method 2
1836

1937
If you can send a PR to this repository then you can create a cherry
2038
pick using the `git` command line tools without requiring any

0 commit comments

Comments
 (0)