summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEd Santiago <santiago@redhat.com>2022-04-27 13:20:55 -0600
committerEd Santiago <santiago@redhat.com>2022-04-27 13:28:34 -0600
commit461b73f563d98d35d825c7b7489d80c353550533 (patch)
tree104db923362e11c88d9b335b2aa9752e96fd47d5
parent9133a6d044c0ab525cc087ca12c1bbc005f5f325 (diff)
downloadpodman-461b73f563d98d35d825c7b7489d80c353550533.tar.gz
podman-461b73f563d98d35d825c7b7489d80c353550533.tar.bz2
podman-461b73f563d98d35d825c7b7489d80c353550533.zip
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>
-rw-r--r--.github/PULL_REQUEST_TEMPLATE.md16
1 files changed, 16 insertions, 0 deletions
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
+
+```