|
15 | 15 | add appropriate labels to your PR as shown below. Three positive reviews are required.
|
16 | 16 | 4. Once the required passing reviews have been obtained, you are ready to request that your PR
|
17 | 17 | be included in the next `devnet` deploy. To do this, you should open a companion PR merging
|
18 |
| - your branch into the `devnet-ready` branch. You must include a link to the parent PR in the |
19 |
| - description and preface your PR title with "(Devnet Ready)" or the PR will be |
20 |
| - closed/ignored. |
| 18 | + a copy of your branch into the `devnet-ready` branch. You must include a link to the parent |
| 19 | + PR in the description and preface your PR title with "(Devnet Ready)" or the PR will be |
| 20 | + closed/ignored. Your companion PR should have the `devnet-companion` label. |
21 | 21 | 5. A core team administrator will review your "(Devnet Ready)" PR, verifying that it logically
|
22 | 22 | matches the changes introduced in the parent PR (there will sometimes be minor differences
|
23 | 23 | due to merge conflicts) and will either request changes or approve the PR and merge it. Once
|
|
86 | 86 | | `runtime` | PR contains substantive changes to runtime / pallet code | none |
|
87 | 87 | | `breaking-change` | PR requires synchronized changes with bittensor | Triggers an automatic bot message so the relevant teams are made aware of the change well in advance |
|
88 | 88 | | `migration` | PR contains one or more migrations | none |
|
| 89 | +| `devnet-companion` | Designates a devnet companion PR | Presence of `devnet-companion` label is checked | |
89 | 90 | | `devnet-ready` | PR's branch has been merged into the `devnet-ready` branch and will be included in the next `devnet` deploy | none |
|
90 | 91 | | `on-devnet` | PR has been deployed to `devnet` | Removes `devnet-ready` |
|
91 | 92 | | `devnet-pass` | PR has passed manual testing on `devnet` | `devnet-pass` or `devnet-skip` required |
|
92 | 93 | | `devnet-skip` | Allows a critical hotfix PR to skip required testing on `devnet` | `devnet-pass` or `devnet-skip` required |
|
93 | 94 | | `devnet-fail` | PR has failed manual testing on `devnet` and requires modification | none |
|
| 95 | +| `testnet-companion` | Designates a testnet companion PR | Presence of `testnet-companion` label is checked | |
94 | 96 | | `on-testnet` | PR has been deployed to `testnet` | none |
|
95 | 97 | | `testnet-pass` | PR has passed manual testing on `testnet` | `testnet-pass` or `testnet-skip` required |
|
96 | 98 | | `testnet-skip` | Allows a critical hotfix PR to skip required manual testing and SOP on `testnet` | `testnet-pass` or `testnet-skip` required |
|
|
0 commit comments