41 lines
1.4 KiB
Markdown
41 lines
1.4 KiB
Markdown
# ISSUE _NUMBER_ - PULL_REQUEST_TITLE
|
|
|
|
Fixes # (issue)
|
|
|
|
## Description
|
|
|
|
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.
|
|
|
|
List here your changes
|
|
|
|
- I made this...
|
|
- I made also that...
|
|
|
|
## Type of change
|
|
|
|
Please select relevant options.
|
|
|
|
- [ ] 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
|
|
|
|
## Checklist
|
|
|
|
- [ ] My code follows the contribution 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
|
|
- [ ] My changes generate no new warnings
|
|
- [ ] I formatted the code with `cargo fmt`
|
|
- [ ] I checked my code using `cargo clippy` and reports no warnings
|
|
- [ ] I have added tests that prove my fix is effective or that my feature works
|
|
- [ ] I have introduced no new *C-bindings*
|
|
- [ ] The changes I've made are Windows, MacOS, UNIX, Linux compatible (or I've handled them using `cfg target_os`)
|
|
- [ ] I increased or maintained the code coverage for the project, compared to the previous commit
|
|
|
|
## Acceptance tests
|
|
|
|
wait for a *project maintainer* to fulfill this section...
|
|
|
|
- [ ] regression test: ...
|