From 23e82c9abd227ee5c8827cf06307be110088f458 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Gon=C3=A7alo=20Heleno?=
 <33546359+lentidas@users.noreply.github.com>
Date: Fri, 24 Mar 2023 15:39:11 +0100
Subject: [PATCH] docs: add PR template (#32)

---
 .github/pull_request_template.md | 19 +++++++++++++++++++
 1 file changed, 19 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 00000000..4f71a770
--- /dev/null
+++ b/.github/pull_request_template.md
@@ -0,0 +1,19 @@
+## Description of the changes
+
+_In this section, explain **what and why** not how._
+
+_In most cases, you can leave out details about how a change has been made. Code is generally self-explanatory in this regard (and if the code is so complex that it needs to be explained in prose, that’s what source comments are for). Just focus on making clear the reasons why you made the change in the first place, the way things worked before the change (and what was wrong with that), the way they work now, and why you decided to solve it the way you did._
+
+## Breaking change
+
+- [ ] No
+- [ ] Yes (in the Helm chart(s)): _indicate the chart, version & release note link_
+- [ ] Yes (in the module itself): _give an explanation of the breaking change_
+
+## Tests executed on which distribution(s)
+
+- [ ] KinD
+- [ ] AKS (Azure)
+- [ ] EKS (AWS)
+- [ ] Scaleway
+- [ ] SKS (Exoscale)