Show More
@@ -18,9 +18,13 b' All pull requests should usually be made against ``master``, if a Pull Request' | |||
|
18 | 18 | need to be backported to an earlier release; then it should be tagged with the |
|
19 | 19 | correct ``milestone``. |
|
20 | 20 | |
|
21 | If you are an admin on the IPython repository just mention the **backport bot** to | |
|
22 | do the work for you. The bot is evolving so instructions may be different. At | |
|
23 | the time of this writing you can use:: | |
|
21 | If you tag a pull request with a milestone **before** merging the pull request, | |
|
22 | and the base ref is `master`, then our backport bot should automatically create | |
|
23 | a corresponding pull-request that backport on the correct branch. | |
|
24 | ||
|
25 | If you are an admin on the IPython repository you can also just mention the | |
|
26 | **backport bot** to do the work for you. The bot is evolving so instructions may | |
|
27 | be different. At the time of this writing you can use:: | |
|
24 | 28 | |
|
25 | 29 | @meeseeksdev[bot] backport [to <branchname>] |
|
26 | 30 | |
@@ -33,6 +37,9 b' backport to.' | |||
|
33 | 37 | The ``@`` and ``[dev]`` when mentioning the bot should be optional and can |
|
34 | 38 | be omitted. |
|
35 | 39 | |
|
40 | If the pull request cannot be automatically backported, the bot should tell you | |
|
41 | so on the PR and apply a "Need manual backport" tag to the origin PR. | |
|
42 | ||
|
36 | 43 | |
|
37 | 44 | Backport with ghpro |
|
38 | 45 | ------------------- |
General Comments 0
You need to be logged in to leave comments.
Login now