Update process for status-go PR to make testing mandatory

This commit is contained in:
fryorcraken.eth 2024-06-18 10:19:45 +10:00
parent 9ac880ad26
commit 8e640674ab
No known key found for this signature in database
GPG Key ID: A82ED75A8DFC50A4
1 changed files with 2 additions and 2 deletions

View File

@ -41,7 +41,7 @@ What is the impact of these changes on the end user (before/after behaviour)
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.
- [ ] 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.
-->