|
1 | 1 | --- |
2 | 2 | name: Pull Request |
3 | 3 | about: Propose a change to the project |
4 | | -title: 'feat(scope): describe your change' |
5 | | -labels: '' |
6 | | -assignees: '' |
7 | | - |
| 4 | +title: "feat(scope): describe your change" |
| 5 | +labels: "" |
| 6 | +assignees: "" |
8 | 7 | --- |
9 | 8 |
|
10 | 9 | **Description** |
11 | 10 |
|
12 | | -Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. |
| 11 | +<!-- Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. --> |
13 | 12 |
|
14 | 13 | **Fixes** (issue) |
15 | 14 |
|
16 | 15 | **Type of change** |
17 | 16 |
|
18 | | -Please update the title of your PR to match the type of change. The title will be used for the commit message and the changelog. |
19 | | - |
20 | | -The `(scope)` is optional and refers to the part of the codebase you're changing (e.g., `feat(search)`, `fix(ci)`). |
21 | | - |
22 | | -- [ ] `fix`: A bug fix |
23 | | -- [ ] `feat`: A new feature |
24 | | -- [ ] `feat!`: A breaking change |
25 | | -- [ ] `docs`: Documentation only changes |
26 | | -- [ ] `chore`: Changes to the build process or auxiliary tools |
27 | | -- [ ] `refactor`: A code change that neither fixes a bug nor adds a feature |
28 | | -- [ ] `perf`: A code change that improves performance |
29 | | -- [ ] `test`: Adding missing tests or correcting existing tests |
30 | | -- [ ] `style`: Changes that do not affect the meaning of the code |
31 | | -- [ ] `ci`: Changes to our CI configuration files and scripts |
32 | | -- [ ] `revert`: Reverts a previous commit |
| 17 | +<!-- Please update the title of your PR to match the type of change. The title will be used for the commit message and the changelog. --> |
| 18 | +<!----> |
| 19 | +<!-- The `(scope)` is optional and refers to the part of the codebase you're changing (e.g., `feat(search)`, `fix(ci)`). --> |
| 20 | + |
| 21 | +<!-- - [ ] `fix`: A bug fix --> |
| 22 | +<!-- - [ ] `feat`: A new feature --> |
| 23 | +<!-- - [ ] `feat!`: A breaking change --> |
| 24 | +<!-- - [ ] `docs`: Documentation only changes --> |
| 25 | +<!-- - [ ] `chore`: Changes to the build process or auxiliary tools --> |
| 26 | +<!-- - [ ] `refactor`: A code change that neither fixes a bug nor adds a feature --> |
| 27 | +<!-- - [ ] `perf`: A code change that improves performance --> |
| 28 | +<!-- - [ ] `test`: Adding missing tests or correcting existing tests --> |
| 29 | +<!-- - [ ] `style`: Changes that do not affect the meaning of the code --> |
| 30 | +<!-- - [ ] `ci`: Changes to our CI configuration files and scripts --> |
| 31 | +<!-- - [ ] `revert`: Reverts a previous commit --> |
33 | 32 |
|
34 | 33 | **How Has This Been Tested?** |
35 | 34 |
|
36 | | -Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration. |
| 35 | +<!-- Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration. --> |
37 | 36 |
|
38 | 37 | - [ ] Test A |
39 | 38 | - [ ] Test B |
|
0 commit comments