|
| 1 | +<!-- IMPORTANT: |
| 2 | +- Please do not create a pull request without creating an issue (bugs) or new discussion (features) first. |
| 3 | +- Any change needs to be discussed before proceeding. Failure to do so may result in the rejection of the pull request. |
| 4 | +- A similar PR may already be submitted! Please check before creating one. |
| 5 | +- Please read the 3 guide beforehand. |
| 6 | +- Branches MUST have descriptive names that start with either the `fix/`, `feature/` or `improvement/` prefixes. |
| 7 | +Good examples are: `fix/pick-directory`, `feature/add-thumbnail-support` or `improvement/reorder-classes`. |
| 8 | +- Provide a general summary of your changes in the title above. |
| 9 | +--> |
| 10 | + |
| 11 | +### Summary |
| 12 | + |
| 13 | +This PR fixes/implements the following **bugs/features**: |
| 14 | + |
| 15 | +- Bug 1: ... |
| 16 | +- Bug 2: ... |
| 17 | +- Feature 1: ... |
| 18 | +- Feature 2: ... |
| 19 | +- Breaking changes: ... |
| 20 | + |
| 21 | +--- |
| 22 | + |
| 23 | +### Motivation |
| 24 | + |
| 25 | +<!-- You can skip this if you're fixing a typo or an open bug issue. --> |
| 26 | + |
| 27 | +<!-- Explain the motivation for making this change. Why is this change required? What existing problem does the pull request solve? --> |
| 28 | +<!-- Example: When "Adding a function to do X", explain why it is necessary to have a way to do X. --> |
| 29 | +<!-- Current behavior -> new behavior --> |
| 30 | + |
| 31 | +```txt |
| 32 | +
|
| 33 | +``` |
| 34 | + |
| 35 | +--- |
| 36 | + |
| 37 | +### How Has This Been Tested? |
| 38 | + |
| 39 | +<!--- Please describe in detail how you tested your changes. --> |
| 40 | +<!--- Provide details about your test environment and the tests you performed. --> |
| 41 | +<!--- See how your change affects other areas of the code. --> |
| 42 | + |
| 43 | +```txt |
| 44 | +
|
| 45 | +``` |
| 46 | + |
| 47 | +--- |
| 48 | + |
| 49 | +### Types of changes |
| 50 | + |
| 51 | +<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> |
| 52 | + |
| 53 | +- [ ] Bug fix (non-breaking change which fixes an issue). |
| 54 | +- [ ] New feature (non-breaking change which adds functionality). |
| 55 | +- [ ] Code style update (formatting, renaming). |
| 56 | +- [ ] Refactoring (no functional changes, no api changes). |
| 57 | +- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected). |
| 58 | +- [ ] Documentation content changes. |
| 59 | +- [ ] Other (please describe): |
| 60 | + |
| 61 | +--- |
| 62 | + |
| 63 | +### Checklist |
| 64 | + |
| 65 | +<!--- Go over all the following points, and put an `x` in all the boxes that apply. --> |
| 66 | + |
| 67 | +- [ ] My code follows the code style of this project. |
| 68 | +- [ ] My change requires a change to the documentation. |
| 69 | +- [ ] I have updated the documentation accordingly. |
| 70 | + |
| 71 | +--- |
| 72 | + |
| 73 | +### Closing Issues |
| 74 | + |
| 75 | +<!-- Use `closes #XXXX` to auto-close the issue that your PR fixes (if such). --> |
| 76 | + |
| 77 | +--- |
| 78 | + |
| 79 | +### Screenshots |
| 80 | + |
| 81 | +<!-- optional --> |
| 82 | + |
| 83 | +--- |
| 84 | + |
| 85 | + |
| 86 | + |
| 87 | +<!-- Thanks for your contribution! --> |
0 commit comments