status-desktop/.github/pull_request_template.md

48 lines
1.4 KiB
Markdown
Raw Normal View History

### What does the PR do
<!-- Fill in the relevant information below to help us evaluate your proposed changes. -->
### Affected areas
<!-- List the affected areas (e.g wallet, browser, etc..) -->
### StatusQ checklist
- [ ] add documentation if necessary (new component, new feature)
- [ ] update sandbox app
- in case of new component, add new component page
- in case of new features, add variation to existing component page
- nice to have: add it to the demo application as well
- [ ] test changes in both light and dark theme?
2022-07-07 12:55:05 +00:00
### Screenshot of functionality (including design for comparison)
- [ ] I've checked the design and this PR matches it
<!-- screenshot (or gif/video) that demonstrates the functionality, specially important if it's a bug fix. -->
<!-- Uncomment this section for status-go upgrade/dogfooding pull requests
### Impact on end user
What is the impact of these changes on the end user (before/after behaviour)
### How to test
- How should one proceed with testing this PR.
- What kind of user flows should be checked?
### Risk
Described potential risks and worst case scenarios.
Tick **one**:
- [ ] Low risk: 2 devs MUST perform testing as specified above and attach their results as comments to this PR **before** merging.
- [ ] High risk: QA team MUST perform additional testing in the specified affected areas **before** merging.
-->
### Cool Spaceship Picture
<!-- optional but cool -->