From f7f8dc6f1a1ca137f756716cc1b32ce3459df1ba Mon Sep 17 00:00:00 2001
From: Robert Kiss <robert.kiss@getbridge.com>
Date: Fri, 16 Feb 2024 09:55:06 +0100
Subject: [PATCH] DoD-Introduce.PR.template.for.the.engineering.repositories

---
 .github/pull_request_template.md | 29 +++++++++++++++++++++++++++++
 1 file changed, 29 insertions(+)
 create mode 100644 .github/pull_request_template.md

diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
new file mode 100644
index 0000000..01928f1
--- /dev/null
+++ b/.github/pull_request_template.md
@@ -0,0 +1,29 @@
+#### JIRA
+
+#### Changes
+
+-
+
+#### Checklist
+- [ ] Feature Flag Required
+- [ ] Bug
+
+#### Test plan
+
+- [ ] Walk-through
+- [ ] Peer review
+- [ ] Inspection
+  - Detailed steps and prerequisites for validating the change:
+    - <!-- Replace this with the bullet points about the steps how to execute the test -->
+
+#### Risk Analysis - the risk of change is evaluated
+
+- [ ] Low - Majority of the changes are low risk which doesn’t require extra testing, only code review by 1 reviewer
+    - [ ] 1 reviewer
+- [ ] Medium - Some portion of changes are medium risk which need peer testing and review by 2 reviewers
+    - [ ] 2 reviewers
+    - [ ] peer testing
+- [ ] High - A very few breaking changes are high risk and need very throughout testing and review and also coordinated release process.
+    - [ ] 2 reviewers
+    - [ ] peer testing
+    - [ ] coordinated release