|
1 | | -Closes # |
| 1 | +Closes [CH-X](https://metacell.atlassian.net/browse/CH-X) |
2 | 2 |
|
3 | | -Implemented solution: ... |
| 3 | +# Implemented solution |
4 | 4 |
|
5 | | -How to test this PR: ... |
| 5 | +... |
6 | 6 |
|
7 | | -### Sanity checks: |
| 7 | +# How to test this PR |
| 8 | + |
| 9 | +... |
| 10 | + |
| 11 | +# Sanity checks: |
8 | 12 | - [ ] The pull request is explicitly linked to the relevant issue(s) |
9 | 13 | - [ ] The issue is well described: clearly states the problem and the general proposed solution(s) |
10 | | -- [ ] From the issue and the current PR it is explicitly stated how to test the current change |
| 14 | +- [ ] In this PR it is explicitly stated how to test the current change |
11 | 15 | - [ ] The labels in the issue set the scope and the type of issue (bug, feature, etc.) |
| 16 | +- [ ] The relevant components are indicated in the issue (if any) |
12 | 17 | - [ ] All the automated test checks are passing |
13 | | -- [ ] All the linked issues are included in one milestone |
14 | | -- [ ] All the linked issues are in the Review/QA column of the [board](https://app.zenhub.com/workspaces/cloud-harness-5fdb203b7e195b0015a273d7/board) |
| 18 | +- [ ] All the linked issues are included in one Sprint |
| 19 | +- [ ] All the linked issues are in the Review state |
15 | 20 | - [ ] All the linked issues are assigned |
16 | 21 |
|
17 | | -### Breaking changes (select one): |
| 22 | +# Breaking changes (select one): |
18 | 23 | - [ ] The present changes do not change the preexisting api in any way |
19 | | -- [ ] This PR and the issue are tagged as a `breaking-change` |
| 24 | +- [ ] This PR and the issue are tagged as a `breaking-change` and the migration procedure is well described [above](#implemented-solution) |
20 | 25 |
|
21 | | -### Possible deployment updates issues (select one): |
| 26 | +# Possible deployment updates issues (select one): |
22 | 27 | - [ ] There is no reason why deployments based on CloudHarness may break after the current update |
23 | 28 | - [ ] This PR and the issue are tagged as `alert:deployment` |
24 | 29 |
|
|
0 commit comments