46 lines
1.4 KiB
Markdown
46 lines
1.4 KiB
Markdown
## Description
|
|
|
|
<!--
|
|
A clear and concise description of what you changed and why.
|
|
Don't forget to mention which tickets this closes (if any).
|
|
Use following syntax to close them automatically on merge: closes #<number>
|
|
-->
|
|
|
|
## Screenshots
|
|
|
|
<!--
|
|
If your changes are user facing, please add screenshots of the new UI.
|
|
You can also create a video to showcase your changes (useful to show UX).
|
|
-->
|
|
|
|
## Additional Context
|
|
|
|
<!--
|
|
You can mention here anything that you think is relevant for this PR. Some examples:
|
|
* You encountered something that you didn't understand while working on this PR
|
|
* You were not sure about something you did but did not find a better way
|
|
* You initially had a different approach but went with a different approach for some reason
|
|
-->
|
|
|
|
## Checklist
|
|
|
|
**Are your changes backwards compatible? Please answer below:**
|
|
|
|
<!-- put your answer about backwards compatibility here -->
|
|
|
|
<!--
|
|
If your PR is not ready for review yet, please mark your PR as a draft.
|
|
If changes were requested, request a new review when you incorporated the feedback.
|
|
-->
|
|
**On a scale of 1-10 how well and how have you QA'd this change and any features it might affect? Please answer below:**
|
|
|
|
<!-- put your answer about QA here -->
|
|
|
|
**For frontend changes: Tested on mobile? Please answer below:**
|
|
|
|
<!-- put your answer about mobile QA here -->
|
|
|
|
**Did you introduce any new environment variables? If so, call them out explicitly here:**
|
|
|
|
<!-- put your answer about env vars here -->
|