|
1 | | - - **Explanation**: |
2 | | - <!-- |
3 | | - A description of the changes. This can be brief, but it should be clear. |
4 | | - --> |
5 | | - - **Scope**: |
6 | | - <!-- |
7 | | - An assessment of the impact and importance of the changes. For example, can |
8 | | - the changes break existing code? |
9 | | - --> |
10 | | - - **Issues**: |
11 | | - <!-- |
12 | | - References to issues the changes resolve, if any. |
13 | | - --> |
14 | | - - **Original PRs**: |
15 | | - <!-- |
16 | | - Links to mainline branch pull requests in which the changes originated. |
17 | | - --> |
18 | | - - **Risk**: |
19 | | - <!-- |
20 | | - The (specific) risk to the release for taking the changes. |
21 | | - --> |
22 | | - - **Testing**: |
23 | | - <!-- |
24 | | - The specific testing that has been done or needs to be done to further |
25 | | - validate any impact of the changes. |
26 | | - --> |
27 | | - - **Reviewers**: |
28 | | - <!-- |
29 | | - The code owners that GitHub-approved the original changes in the mainline |
30 | | - branch pull requests. If an original change has not been GitHub-approved by |
31 | | - a respective code owner, provide a reason. Technical review can be delegated |
32 | | - by a code owner or otherwise requested as deemed appropriate or useful. |
33 | | - --> |
| 1 | +- **Explanation**: |
| 2 | + <!-- |
| 3 | + A description of the changes. This can be brief, but it should be clear. |
| 4 | + --> |
| 5 | +- **Scope**: |
| 6 | + <!-- |
| 7 | + An assessment of the impact and importance of the changes. For example, can |
| 8 | + the changes break existing code? |
| 9 | + --> |
| 10 | +- **Issues**: |
| 11 | + <!-- |
| 12 | + References to issues the changes resolve, if any. |
| 13 | + --> |
| 14 | +- **Original PRs**: |
| 15 | + <!-- |
| 16 | + Links to mainline branch pull requests in which the changes originated. |
| 17 | + --> |
| 18 | +- **Risk**: |
| 19 | + <!-- |
| 20 | + The (specific) risk to the release for taking the changes. |
| 21 | + --> |
| 22 | +- **Testing**: |
| 23 | + <!-- |
| 24 | + The specific testing that has been done or needs to be done to further |
| 25 | + validate any impact of the changes. |
| 26 | + --> |
| 27 | +- **Reviewers**: |
| 28 | + <!-- |
| 29 | + The code owners that GitHub-approved the original changes in the mainline |
| 30 | + branch pull requests. If an original change has not been GitHub-approved by |
| 31 | + a respective code owner, provide a reason. Technical review can be delegated |
| 32 | + by a code owner or otherwise requested as deemed appropriate or useful. |
| 33 | + --> |
0 commit comments