1 | # Description
|
2 |
|
3 | Please include a summary of the change and which issue is fixed. 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 | **Test Configuration**:
|
24 | * Firmware version:
|
25 | * Hardware:
|
26 | * Toolchain:
|
27 | * SDK:
|
28 |
|
29 | # Checklist:
|
30 |
|
31 | - [ ] My code follows the style guidelines of this project
|
32 | - [ ] I have performed a self-review of my own code
|
33 | - [ ] I have commented my code, particularly in hard-to-understand areas
|
34 | - [ ] I have made corresponding changes to the documentation
|
35 | - [ ] My changes generate no new warnings
|
36 | - [ ] I have added tests that prove my fix is effective or that my feature works
|
37 | - [ ] New and existing unit tests pass locally with my changes
|
38 | - [ ] Any dependent changes have been merged and published in downstream modules |
\ | No newline at end of file |