|
1 | | -<!-- |
2 | | - Thanks for submitting a Pull Request (PR) to this project. Your contribution to this project |
3 | | - is greatly appreciated! |
4 | | -
|
5 | | - Please prefix the PR title with the resource name, e.g. 'ResourceName: My short description'. |
6 | | - If this is a breaking change, then also prefix the PR title with 'BREAKING CHANGE:', |
7 | | - e.g. 'BREAKING CHANGE: ResourceName: My short description'. |
8 | | -
|
9 | | - You may remove this comment block, and the other comment blocks, but please keep the headers |
10 | | - and the task list. |
11 | | ---> |
12 | | - |
13 | | -#### Pull Request (PR) description |
14 | | - |
15 | | -<!-- |
16 | | - Replace this comment block with a description of your PR. |
17 | | ---> |
18 | | - |
19 | | -#### This Pull Request (PR) fixes the following issues |
20 | | - |
21 | | -<!-- |
22 | | - If this PR does not fix an open issue, replace this comment block with None. If this PR |
23 | | - resolves one or more open issues, replace this comment block with a list of the issues using |
24 | | - a GitHub closing keyword, e.g.: |
25 | | -
|
26 | | -- Fixes #123 |
27 | | -- Fixes #124 |
28 | | ---> |
29 | | - |
30 | | -#### Task list |
31 | | - |
32 | | -<!-- |
33 | | - To aid community reviewers in reviewing and merging your PR, please take the time to run |
34 | | - through the below checklist and make sure your PR has everything updated as required. |
35 | | -
|
36 | | - Change to [x] for each task in the task list that applies to your PR. For those task that |
37 | | - don't apply to you PR, leave those as is. |
38 | | ---> |
39 | | - |
40 | | -- [ ] Added an entry to the change log under the Unreleased section of the file CHANGELOG.md. |
41 | | - Entry should say what was changed and how that affects users (if applicable), and |
42 | | - reference the issue being resolved (if applicable). |
43 | | -- [ ] Resource documentation added/updated in README.md. |
44 | | -- [ ] Resource parameter descriptions added/updated in README.md, schema.mof and comment-based |
45 | | - help. |
46 | | -- [ ] Comment-based help added/updated. |
47 | | -- [ ] Localization strings added/updated in all localization files as appropriate. |
48 | | -- [ ] Examples appropriately added/updated. |
49 | | -- [ ] Unit tests added/updated. See [DSC Community Testing Guidelines](https://dsccommunity.org/guidelines/testing-guidelines). |
50 | | -- [ ] Integration tests added/updated (where possible). See [DSC Community Testing Guidelines](https://dsccommunity.org/guidelines/testing-guidelines). |
51 | | -- [ ] New/changed code adheres to [DSC Community Style Guidelines](https://dsccommunity.org/styleguidelines). |
| 1 | +# Description |
| 2 | + |
| 3 | +Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change. |
| 4 | + |
| 5 | +Fixes # (issue) |
| 6 | + |
| 7 | +## Type of change |
| 8 | + |
| 9 | +Please delete options that are not relevant. |
| 10 | + |
| 11 | +- [ ] Bug fix (non-breaking change which fixes an issue) |
| 12 | +- [ ] New feature (non-breaking change which adds functionality) |
| 13 | +- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) |
| 14 | +- [ ] This change requires a documentation update |
| 15 | + |
| 16 | +# How Has This Been Tested? |
| 17 | + |
| 18 | +Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration |
| 19 | + |
| 20 | +- [ ] Test A |
| 21 | +- [ ] Test B |
| 22 | + |
| 23 | + |
| 24 | +# Checklist: |
| 25 | + |
| 26 | +- [ ] My code follows the style guidelines of this project |
| 27 | +- [ ] I have performed a self-review of my code |
| 28 | +- [ ] I have commented my code, particularly in hard-to-understand areas |
| 29 | +- [ ] I have made corresponding changes to the documentation |
| 30 | +- [ ] My changes generate no new warnings |
| 31 | +- [ ] I have added tests or screenshots that prove my fix is effective or that my feature works |
| 32 | +- [ ] Any dependent changes have been merged and published in downstream modules |
| 33 | + |
0 commit comments