34 lines
1.6 KiB
Markdown
34 lines
1.6 KiB
Markdown
|
<!-- Make sure the title includes categorization (i.e. [Bug], [QoL], [Localization]) -->
|
||
|
|
<!-- Make sure that this PR is not overlapping with someone else's work -->
|
||
|
|
<!-- Please try to keep the PR self-contained (and small) -->
|
||
|
|
|
||
|
|
## What are the changes?
|
||
|
|
<!-- Summarize what are the changes from a user perspective on the application -->
|
||
|
|
|
||
|
|
## Why am I doing these changes?
|
||
|
|
<!-- Explain why you decided to introduce these changes -->
|
||
|
|
<!-- Does it come from an issue or another PR? Please link it -->
|
||
|
|
<!-- Explain why you believe this can enhance user experience -->
|
||
|
|
|
||
|
|
## What did change?
|
||
|
|
<!-- Explicitly state what are the changes introduced by the PR -->
|
||
|
|
<!-- You can make use of a comparison between what was the state before and after your PR changes -->
|
||
|
|
|
||
|
|
### Screenshots/Videos
|
||
|
|
<!-- If your change is changing anything on the user experience, please provide visual proofs of it -->
|
||
|
|
<!-- Please take screenshots/videos before and after your changes, to show what is brought by this PR -->
|
||
|
|
|
||
|
|
## How to test the changes?
|
||
|
|
<!-- How can a reviewer test your changes once they check out on your branch? -->
|
||
|
|
<!-- Did you just make use of the `src/overrides.ts` file? -->
|
||
|
|
<!-- Did you introduce any automated tests? -->
|
||
|
|
<!-- Do the reviewer need to do something special in order to test your change? -->
|
||
|
|
|
||
|
|
## Checklist
|
||
|
|
- [ ] There is no overlap with another PR?
|
||
|
|
- [ ] The PR is self-contained and cannot be split into smaller PRs?
|
||
|
|
- [ ] Have I provided a clear explanation of the changes?
|
||
|
|
- [ ] Have I tested the changes (manually)?
|
||
|
|
- [ ] Are all unit tests still passing? (`npm run test`)
|
||
|
|
- [ ] Are the changes visual?
|
||
|
|
- [ ] Have I provided screenshots/videos of the changes?
|