From 6265504cc44872b462a463410f6d4cff77920671 Mon Sep 17 00:00:00 2001
From: tariq1890 <tariq181290@gmail.com>
Date: Fri, 22 Jun 2018 23:02:50 -0700
Subject: [PATCH] Renaming Issue Templates correctly and adding a pull request
 template

---
 .../{issue_template.md => ISSUE_TEMPLATE.md}  |  0
 .github/PULL_REQUEST_TEMPLATE.md              | 22 +++++++++++++++++++
 2 files changed, 22 insertions(+)
 rename .github/{issue_template.md => ISSUE_TEMPLATE.md} (100%)
 create mode 100644 .github/PULL_REQUEST_TEMPLATE.md

diff --git a/.github/issue_template.md b/.github/ISSUE_TEMPLATE.md
similarity index 100%
rename from .github/issue_template.md
rename to .github/ISSUE_TEMPLATE.md
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
new file mode 100644
index 000000000..c890d6713
--- /dev/null
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,22 @@
+<!--  Thanks for sending a pull request!  Here are some tips for you:
+1. If you want *faster* PR reviews, read how: https://github.com/kubernetes/community/blob/master/contributors/guide/pull-requests.md
+-->
+
+**What this PR does / why we need it**:
+
+**Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #
+
+**Special notes for your reviewer**:
+
+**If applicable**:
+- [ ] documentation
+- [ ] unit tests
+- [ ] tested backward compatibility (ie. deploy with previous version, upgrade with this branch)
+
+**Release note**:
+<!--  Steps to write your release note:
+1. Use the release-note-* labels to set the release note state (if you have access)
+2. Enter your extended release note in the below block; leaving it blank means using the PR title as the release note. If no release note is required, just write `NONE`.
+-->
+```release-note
+```