51 lines
1.6 KiB
Markdown
51 lines
1.6 KiB
Markdown
> Pull Request Template
|
|
>
|
|
> Use this template to quickly create a well written pull request. Delete all quotes before creating the pull request.
|
|
|
|
## Description
|
|
|
|
> Please include a summary of the changes and which issue has been fixed. Please also include relevant motivation
|
|
> and context. List any dependencies that are required for this change.
|
|
|
|
Fixes # (issue)
|
|
|
|
> if no issue exists, please create an issue and ask the maintainers about this first
|
|
|
|
|
|
## Type of change
|
|
|
|
> Please delete options that are not 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?
|
|
|
|
> 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.
|
|
> Delete anything that is not important
|
|
|
|
- Manual
|
|
- Jest
|
|
- Cypress
|
|
|
|
### Test Plan
|
|
> Add Testsmith test cases links that relate to this PR
|
|
|
|
### Issues raised during DP testing
|
|
> Link issues raised during DP testing for better visiblity and tracking
|
|
|
|
|
|
## 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
|