| 1 |
<!-- |
| 2 |
Before opening a PR, open a ticket describing the issue or feature the |
| 3 |
PR will address. Follow the steps in CONTRIBUTING.rst. |
| 4 |
|
| 5 |
Replace this comment with a description of the change. Describe how it |
| 6 |
addresses the linked ticket. |
| 7 |
--> |
| 8 |
|
| 9 |
<!-- |
| 10 |
Link to relevant issues or previous PRs, one per line. Use "fixes" to |
| 11 |
automatically close an issue. |
| 12 |
--> |
| 13 |
|
| 14 |
- fixes #<issue number> |
| 15 |
|
| 16 |
<!-- |
| 17 |
Ensure each step in CONTRIBUTING.rst is complete by adding an "x" to |
| 18 |
each box below. |
| 19 |
|
| 20 |
If only docs were changed, these aren't relevant and can be removed. |
| 21 |
--> |
| 22 |
|
| 23 |
Checklist: |
| 24 |
|
| 25 |
- [ ] Add tests that demonstrate the correct behavior of the change. Tests should fail without the change. |
| 26 |
- [ ] Add or update relevant docs, in the docs folder and in code. |
| 27 |
- [ ] Add an entry in `CHANGES.rst` summarizing the change and linking to the issue. |
| 28 |
- [ ] Add `.. versionchanged::` entries in any relevant code docs. |
| 29 |
- [ ] Run `pre-commit` hooks and fix any issues. |
| 30 |
- [ ] Run `pytest` and `tox`, no tests failed. |