|
1 | 1 | ## Description |
2 | 2 |
|
3 | | -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. |
| 3 | +Please include a summary of the change and which issue is fixed. |
4 | 4 |
|
5 | 5 | Fixes # (issue) |
6 | 6 |
|
7 | | -## Change Type (select one) |
| 7 | +## Change Type |
8 | 8 |
|
9 | | -- [ ] 🐛 Bug fix (non-breaking change fixing an issue) |
10 | | -- [ ] ✨ New feature (non-breaking change adding functionality) |
11 | | -- [ ] 💥 Breaking change (fix/feature causing existing functionality to break) |
12 | | -- [ ] 🏗️ Refactoring (code change that neither fixes bug nor adds feature) |
13 | | -- [ ] 📚 Documentation (changes only affecting documentation) |
14 | | -- [ ] 🎨 Styling (changes that do not affect functionality) |
| 9 | +- 🐛 Bug fix (non-breaking change fixing an issue) |
| 10 | +- ✨ New feature (non-breaking change adding functionality) |
| 11 | +- 💥 Breaking change (fix/feature causing existing functionality to break) |
| 12 | +- 🏗️ Refactoring (code change that neither fixes bug nor adds feature) |
| 13 | +- 📚 Documentation (changes only affecting documentation) |
| 14 | +- 🎨 Styling (changes that do not affect functionality) |
15 | 15 |
|
16 | | -## PR Scope Checklist |
| 16 | +## Related Issues |
17 | 17 |
|
18 | | -_This checklist is mandatory for all PRs._ |
19 | | - |
20 | | -- [ ] **PR has a clear, single purpose:** The title and description of the PR clearly state the purpose of the change. |
21 | | -- [ ] **All changes relate to the stated objective:** The code changes should be directly related to the purpose of the PR. |
22 | | -- [ ] **No unrelated cleanup or refactoring:** The PR should not contain any changes that are not directly related to the stated objective. |
23 | | -- [ ] **Title and description match the actual changes:** The title and description should accurately reflect the changes in the PR. |
24 | | -- [ ] **Tests cover the specific change scope:** The tests should be focused on the changes in the PR and should not include unrelated tests. |
25 | | - |
26 | | -## Impact Assessment |
27 | | - |
28 | | -- [ ] Changes are **backward compatible** (or breaking changes are documented) |
29 | | -- [ ] **Tests** are added/updated for new functionality |
30 | | -- [ ] **Documentation** is updated if needed |
31 | | -- [ ] **ADR** is created/updated for significant architectural changes |
| 18 | +Closes #(issue_number) |
0 commit comments