35 lines
1.3 KiB
Markdown
35 lines
1.3 KiB
Markdown
## Description
|
|
[Provide a brief description of the changes in this PR]
|
|
|
|
## Related Issue
|
|
[Link to the issue this PR addresses, if applicable]
|
|
|
|
## Motivation and Context
|
|
[Explain why this change is needed and how it benefits the project]
|
|
|
|
## Type of Change
|
|
Please check the options that are relevant.
|
|
- [ ] Bug fix (non-breaking change which fixes an issue)
|
|
- [ ] New feature (non-breaking change which adds functionality)
|
|
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
|
|
- [ ] This change requires a documentation update
|
|
|
|
## How Has This Been Tested?
|
|
[Describe the tests you ran to verify your changes. Provide instructions so we can reproduce.]
|
|
|
|
## Checklist:
|
|
- [ ] My code follows the style guidelines of this project
|
|
- [ ] I have performed a self-review of my own code
|
|
- [ ] I have commented my code, particularly in hard-to-understand areas
|
|
- [ ] I have made corresponding changes to the documentation
|
|
- [ ] My changes generate no new warnings
|
|
- [ ] I have added tests that prove my fix is effective or that my feature works
|
|
- [ ] New and existing unit tests pass locally with my changes
|
|
- [ ] Any dependent changes have been merged and published in downstream modules
|
|
|
|
## Screenshots (if appropriate):
|
|
[Add screenshots here if applicable]
|
|
|
|
## Additional Notes:
|
|
[Add any other information about the PR here]
|