From 461b73f563d98d35d825c7b7489d80c353550533 Mon Sep 17 00:00:00 2001
From: Ed Santiago <santiago@redhat.com>
Date: Wed, 27 Apr 2022 13:20:55 -0600
Subject: Github PR template: add release-note block

Initial step toward automating the collection & generation
of release notes: add a markdown release-note block to our
PR template. This will be reaped by an existing Kubernetes
tool and gathered into a document that can be used as a
starting point for future releases.

Many more followup steps to come.

Signed-off-by: Ed Santiago <santiago@redhat.com>
---
 .github/PULL_REQUEST_TEMPLATE.md | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index 16ec09357..9a4563308 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -9,3 +9,19 @@ Finally, be sure to sign commits with your real name.  Since by opening
 a PR you already have commits, you can add signatures if needed with
 something like `git commit -s --amend`.
 -->
+
+#### Does this PR introduce a user-facing change?
+
+<!--
+If no, just write `None` in the release-note block below. If yes, a release note
+is required: Enter your extended release note in the block below. If the PR
+requires additional action from users switching to the new release, include the
+string "action required".
+
+For more information on release notes please follow the kubernetes model:
+https://git.k8s.io/community/contributors/guide/release-notes.md
+-->
+
+```release-note
+
+```
-- 
cgit v1.2.3-54-g00ecf