From 58eeafadd7601cacaad1b1dd50089a5ebe9b89fb Mon Sep 17 00:00:00 2001
From: oscollabus <oshoval@redhat.com>
Date: Tue, 26 Jul 2022 13:34:58 +0300
Subject: [PATCH] Add github issue/PR templates (#57)

Similar to other kubevirt projects they include the release_note field
at the PR making easier to modify it.

Signed-off-by: Or Shoval <oshoval@redhat.com>
---
 .github/PULL_REQUEST_TEMPLATE.md | 28 ++++++++++++++++++++++++++++
 1 file changed, 28 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..f9ae7ec0
--- /dev/null
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,28 @@
+<!-- Thanks for sending a pull request!
+
+Before you click the 'Create pull request' make sure that:
+- This PR introduces a single feature of fix, just one
+- This PR does not leave the main branch broken
+- Every commit in this PR has a commit message explaining what do you change,
+  why and what is the outcome
+- If your change introduces a complex concept or a change to user interaction
+  with the project or the application, make sure to document it
+
+If you don't comply with these rules, you waste your energy, time of reviewers
+and cause suffering of future generations.
+-->
+
+**What this PR does / why we need it**:
+
+**Special notes for your reviewer**:
+
+**Release note**:
+<!--  Write your release note:
+1. Enter your extended release note in the below block. If the PR requires additional action from users switching to the new release, include the string "action required".
+2. Follow the instructions for writing a release note from k8s: https://git.k8s.io/community/contributors/guide/release-notes.md
+3. If no release note is required, just write "NONE".
+-->
+
+```release-note
+
+```