|
1 | | -<!-- |
2 | | -⚠️ If you do not respect this template, your pull request will be closed. |
3 | | -⚠️ Your pull request title should be short detailed and understandable for all. |
4 | | -⚠️ Also, please add it in the CHANGELOG file under Unreleased section. |
5 | | -⚠️ If your pull request fixes an open issue, please link to the issue. |
| 1 | +### Summary |
6 | 2 |
|
7 | | -✅ I have added the tests to cover my changes. |
8 | | -✅ I have updated the documentation accordingly. |
9 | | -✅ I have read the CONTRIBUTING document. |
10 | | ---> |
| 3 | +Please describe what this PR changes as concisely as possible. Link to the issue(s) |
| 4 | +that this addresses, if any. |
11 | 5 |
|
12 | | -### Summary |
| 6 | +### Details and comments |
13 | 7 |
|
| 8 | +Some details that should be in this section include: |
14 | 9 |
|
| 10 | +- Why this change was necessary |
| 11 | +- What alternative solutions were considered and why the current solution was chosen |
| 12 | +- What tests and documentation have been added/updated |
| 13 | +- What do users and developers need to know about this change |
15 | 14 |
|
16 | | -### Details and comments |
| 15 | +Note that this entire PR description field will be used as the commit message upon |
| 16 | +merge, so please keep it updated along with the PR. Secondary discussions, such as |
| 17 | +intermediate testing and bug statuses that do not affect the final PR, should be in the |
| 18 | +PR comments. |
17 | 19 |
|
| 20 | +### PR checklist (delete when all criteria are met) |
18 | 21 |
|
| 22 | +- [ ] I have read the contributing guide `CONTRIBUTING.md`. |
| 23 | +- [ ] I have added the tests to cover my changes. |
| 24 | +- [ ] I have updated the documentation accordingly. |
| 25 | +- [ ] I have added a release note file using `reno` if this change needs to be |
| 26 | + documented in the release notes. |
0 commit comments