From 1f7534c54c04dbe32eafa44afd507be464e00197 Mon Sep 17 00:00:00 2001
From: gabemontero <gmontero@redhat.com>
Date: Wed, 10 Feb 2021 20:21:15 -0500
Subject: [PATCH] add pull request template to integrate with prow release-note
 plugin

---
 .github/pull_request_template.md | 47 ++++++++++++++++++++++++++++++++
 1 file changed, 47 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 0000000000..5485a9bb3c
--- /dev/null
+++ b/.github/pull_request_template.md
@@ -0,0 +1,47 @@
+# Changes
+
+<!-- 🎉🎉🎉 Thank you for the PR!!! 🎉🎉🎉 -->
+
+<!-- Describe your changes here- ideally you can get that description straight from
+your descriptive commit message(s)! -->
+
+<!-- If this PR fixes a GitHub issue, please mention it like so:
+
+Fixes #<insert issue number here>
+
+-->
+
+# Submitter Checklist
+
+See [the contributor guide](https://github.com/shipwright-io/build/blob/master/CONTRIBUTING.md)
+for details on coding conventions, github and prow interactions, and the code review process.
+
+# Release Notes
+
+<!--
+Describe any user facing changes here, or delete this block.
+
+Examples of user facing changes:
+- API changes
+- Bug fixes
+- Any changes in behavior
+- Changes requiring upgrade notices or deprecation warnings
+
+For pull requests with a release note:
+
+```release-note
+Your release note here
+```
+
+For pull requests that require additional action from users switching to the new release, include the string "action required" (case insensitive) in the release note:
+
+```release-note
+action required: your release note here
+```
+
+For pull requests that don't need to be mentioned at release time, use the `/release-note-none` Prow command to add the `release-note-none` label to the PR. You can also write the string "NONE" as a release note in your PR description:
+
+```release-note
+NONE
+```
+-->