From 1e785b21168e9de97ecf39faebaf84838b74e1e4 Mon Sep 17 00:00:00 2001
From: "fryorcraken.eth" <git@fryorcraken.xyz>
Date: Tue, 18 Jun 2024 10:15:02 +1000
Subject: [PATCH] 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.
---
 .github/pull_request_template.md | 23 ++++++++++++++++++++++-
 1 file changed, 22 insertions(+), 1 deletion(-)

diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index b2d26474e9..1bf417756a 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -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.
+
+-->