]>
Commit | Line | Data |
---|---|---|
1 | ## Description | |
2 | ||
3 | <!-- Please include a summary of the change, with motivation and context --> | |
4 | ||
5 | ## Related issues | |
6 | ||
7 | <!-- If suggesting a new feature or change, please discuss it in an issue first --> | |
8 | <!-- If fixing a bug, there should be an issue describing it with steps to reproduce --> | |
9 | <!-- start with closing keywords if any apply: https://docs.github.com/en/enterprise/2.16/user/github/managing-your-work-on-github/closing-issues-using-keywords --> | |
10 | ||
11 | ## Has this been tested? | |
12 | ||
13 | <!--- Put an `x` in the box that applies: --> | |
14 | - [ ] 👍 yes, I added tests to the test suite | |
15 | - [ ] 👍 yes, light tests as follows are enough | |
16 | - [ ] 💭 no, because this PR is a draft and still needs work | |
17 | - [ ] 🙅 no, because they aren't needed | |
18 | - [ ] 🙋 no, because I need help | |
19 | ||
20 | <!-- | |
21 | If you didn't test via unit-testing, you will still be asked to prove your fix is effective, doesn't have side-effects, or that your feature simply works: | |
22 | ||
23 | Please describe the tests that you ran to verify your changes. | |
24 | Provide instructions so we can reproduce. | |
25 | Please also list any relevant details for your test configuration(s): | |
26 | --> | |
27 | ||
28 | ## Screenshots | |
29 | ||
30 | <!-- delete if not relevant --> |