33 lines
1.1 KiB
Markdown
33 lines
1.1 KiB
Markdown
|
## Type of change
|
||
|
- [ ] Bug fix
|
||
|
- [ ] New feature development
|
||
|
- [ ] Tech debt (refactoring, code cleanup, dependency upgrades, etc)
|
||
|
- [ ] Build/deploy pipeline (DevOps)
|
||
|
- [ ] Other
|
||
|
|
||
|
## Objective
|
||
|
<!--Describe what the purpose of this PR is. For example: what bug you're fixing or what new feature you're adding-->
|
||
|
|
||
|
|
||
|
|
||
|
## Code changes
|
||
|
<!--Explain the changes you've made to each file or major component. This should help the reviewer understand your changes-->
|
||
|
<!--Also refer to any related changes or PRs in other repositories-->
|
||
|
|
||
|
* **file.ext:** Description of what was changed and why
|
||
|
|
||
|
## Screenshots
|
||
|
<!--Required for any UI changes. Delete if not applicable-->
|
||
|
|
||
|
|
||
|
|
||
|
## Testing requirements
|
||
|
<!--What functionality requires testing by QA? This includes testing new behavior and regression testing-->
|
||
|
|
||
|
|
||
|
|
||
|
## Before you submit
|
||
|
- [ ] I have added **unit tests** where it makes sense to do so (encouraged but not required)
|
||
|
- [ ] This change requires a **documentation update** (notify the documentation team)
|
||
|
- [ ] This change has particular **deployment requirements** (notify the DevOps team)
|