Add instructions for status-go PRs

Define a process for status-go PRs as more of those are expected to be
opened by the Waku team.
This commit is contained in:
fryorcraken.eth 2024-06-18 10:15:02 +10:00 committed by fryorcraken
parent e2949ad6e7
commit 1e785b2116
No known key found for this signature in database
GPG Key ID: A82ED75A8DFC50A4
1 changed files with 22 additions and 1 deletions

View File

@ -23,4 +23,25 @@
### Cool Spaceship Picture
<!-- optional but cool ->
<!-- optional but cool -->
<!-- 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.
- [ ] High risk: QA team perform additional testing in the specified affected areas.
-->