From a5fcd70b7660358ddd57c187b9bc2c3aae67bd54 Mon Sep 17 00:00:00 2001
From: Ashley Davis <ashley.davis@jetstack.io>
Date: Mon, 24 Jan 2022 15:29:48 +0000
Subject: [PATCH] update PR template to be simpler and mention allowing edits

Signed-off-by: Ashley Davis <ashley.davis@jetstack.io>
---
 .github/PULL_REQUEST_TEMPLATE.md | 35 +++++++++++++++++++++-----------
 1 file changed, 23 insertions(+), 12 deletions(-)

diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index f9d464f7d..efe0df545 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -1,20 +1,31 @@
-<!--  Thanks for sending a pull request!  Here are some tips for you:
-1. If this is your first time, read our contributor guidelines https://git.k8s.io/community/contributors/guide#your-first-contribution and developer guide https://git.k8s.io/community/contributors/devel/development.md#development-guide
-2. If you want *faster* PR reviews, read how: https://git.k8s.io/community/contributors/guide/pull-requests.md#best-practices-for-faster-reviews
-3. Follow the instructions for writing a release note: https://git.k8s.io/community/contributors/guide/release-notes.md
-4. If the PR is unfinished, see how to mark it: https://git.k8s.io/community/contributors/guide/pull-requests.md#marking-unfinished-pull-requests
+<!--
+
+Thanks for opening a pull request! Here are some tips to get everything merged smoothly:
+
+1. Read our contributor guidelines: https://cert-manager.io/docs/contributing/
+
+2. Make sure your commits are signed off: https://cert-manager.io/docs/contributing/sign-off/
+
+3. If the PR is unfinished, raise it as a draft or prefix the title with "WIP:" so it's clear to everyone.
+
+4. Be sure to allow edits from maintainers so it's easier for us to help: https://help.github.com/en/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork
+
 -->
 
-**What this PR does / why we need it**:
+## Pull Request Motivation
 
-**Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #
+<!-- Explain the motivation behind this PR. If there's a related issue or PR, link to it here! -->
 
-**Special notes for your reviewer**:
+## Release Note
+
+<!--
+
+Should we mention this PR in release notes? If so, replace "NONE" with a line of text explaining what changed!
+
+For more details, see: https://git.k8s.io/community/contributors/guide/release-notes.md
 
-**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
+NONE
 ```