Add different PR templates to make sure no release work is missed, and dev PRs are actually filled with useful information

This commit is contained in:
Daniel Cronqvist 2024-09-07 21:39:48 +02:00
parent 914a667c35
commit 40106b5472
2 changed files with 25 additions and 0 deletions

View file

@ -0,0 +1,15 @@
## Description
<!-- Provide a clear and concise description of the changes introduced by this PR. Include the purpose and context for these changes. -->
### Type of Change
- [ ] 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)
- [ ] Documentation update
## Checklist
- [ ] Tests have been added/updated to cover new functionality.
- [ ] Documentation has been updated for all new changes (e.g., usage examples, API documentation).

View file

@ -0,0 +1,10 @@
# Release vX.Y.Z
<!-- Include a description of what is breaking/new/patched in this release. -->
## Checklist for a release PR
- [ ] Version compatibility matrix has been updated.
- [ ] Tests have been added/updated to cover new functionality.
- [ ] Documentation has been updated for all new changes (e.g., usage examples, API documentation).