From 76087fc833d4ef924b134a3f15d0a7bc68d638aa Mon Sep 17 00:00:00 2001
From: Brian Downs <brian.downs@gmail.com>
Date: Tue, 5 May 2020 15:14:38 -0700
Subject: [PATCH] update template

---
 .github/PULL_REQUEST_TEMPLATE.md | 46 +++++++++++++++++++++++++++++---
 1 file changed, 42 insertions(+), 4 deletions(-)

diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index b3a459565d..d3cac96fbd 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -1,7 +1,45 @@
-**- Description**
+<!-- HTML Comments can be left in place or removed, dealers choice. They are present simply to guide you on your pull-request journey. --> 
+Proposed changes
+======
+<!-- 
 
-**- How to verify**
+Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.
 
-**- Related Issue**
+-->
 
-( What issue does this pull request resolve? If there is no issue, please create one [here](https://github.com/rancher/k3s/issues). )
+Types of changes
+======
+<!-- 
+
+What types of changes does your code introduce to Rancher?
+- Bugfix (non-breaking change which fixes an issue)
+- New feature (non-breaking change which adds functionality)
+- Breaking change (fix or feature that would cause existing functionality to not work as expected)
+
+-->
+
+Verification
+======
+<!---
+
+How can the changes be verified? Please provide whatever additional information necessary to help verify the proposed changes.
+
+-->
+
+Linked Issues
+======
+<!--
+
+Link any related issues, pull-requests, or commit hashes that are relavent to this pull-request.
+
+If you are opening a PR without a corresponding issue create an issue before you do, [here](https://github.com/rancher/k3s/issues). This will help QA massively. PR's opened without linked issues will not be merged until an issue is created and linked here. 
+
+--> 
+
+Further comments
+======
+<!-- 
+
+If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc... 
+
+-->
\ No newline at end of file