|
|
@@ -7,20 +7,15 @@ Please make sure that the pull request is limited to one type (docs, feature, et
|
|
|
<!-- If this pull request closes an issue, please mention the issue number below -->
|
|
|
Closes # <!-- Issue # here -->
|
|
|
|
|
|
-### Description
|
|
|
-<!-- Add a brief description of the pull request -->
|
|
|
+<!-- Add an introduction into what this PR tries to solve in a couple of sentences -->
|
|
|
+
|
|
|
+### What's changed
|
|
|
+<!-- Describe point by point the different things you have changed in this PR -->
|
|
|
|
|
|
<!-- You can also choose to add a list of changes and if they have been completed or not by using the markdown to-do list syntax
|
|
|
- [ ] Not Completed
|
|
|
- [x] Completed
|
|
|
-->
|
|
|
|
|
|
-### Checks
|
|
|
-<!-- Make sure your pull request passes the CI checks and do check the following fields as needed - -->
|
|
|
-- [ ] My pull request adheres to the code style of this project
|
|
|
-- [ ] My code requires changes to the documentation
|
|
|
-- [ ] I have updated the documentation as required
|
|
|
-- [ ] All the tests have passed
|
|
|
-
|
|
|
-### Additional Information
|
|
|
-<!-- Any additional information like breaking changes, dependencies added, screenshots, comparisons between new and old behaviour, etc. -->
|
|
|
+### Notes to reviewers
|
|
|
+<!-- Any information you feel the reviewer should know about when reviewing your PR -->
|
Andrew Bastin