x/urfave-cli
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Use a more k8s/release friendly PR template.

Browse Source
This commit is contained in:
j0n3lson 2020-01-09 17:11:23 -08:00
parent 3b8f4b9b22
commit ab81cf7eac
1 changed files with 33 additions and 23 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

56
.github/pull_request_template.md vendored
View File

@ -4,38 +4,57 @@
If a section of the PR template does not apply to this PR, then delete that section.
-->
## Motivation
## What type of PR is this?
_(fill-in or delete this section)_
_(REQUIRED)_
<!--
/kind bug
/kind cleanup
/kind documentation
/kind feature
-->
## What this PR does / why we need it:
_(REQUIRED)_
<!--
What goal is this change working towards?
Provide a bullet pointed summary of how each file was changed.
Briefly explain any decisions you made with respect to the changes.
Include anything here that you didn't include in *Release Notes*
above, such as changes to CI or changes to internal methods.
-->
## Which issue(s) this PR fixes:
_(REQUIRED)_
<!--
If this PR fixes one of more issues, list them here.
One line each, like so:
Fixes #123
Fixes #39
-->
## Release Notes
## Special notes for your reviewer:
_(fill-in or delete this section)_
<!--
If this PR makes user facing changes, please describe them here.
This description will be copied into the release notes, whenever
the next version is released. Keep this section short, and
focus on high level changes.
Is there any particular feedback you would / wouldn't like?
Which parts of the code should reviewers focus on?
-->
## Changes
## Release Notes
_(fill-in or delete this section)_
_(REQUIRED)_
<!--
Provide a bullet pointed summary of how each file was changed.
Briefly explain any decisions you made with respect to the changes.
Include anything here that you didn't include in *Release Notes*
above, such as changes to CI or changes to internal methods.
If this PR makes user facing changes, please describe them here. This
description will be copied into the release notes/changelog, whenever the
next version is released. Keep this section short, and focus on high level
changes.
-->
## Testing
@ -44,13 +63,4 @@ _(fill-in or delete this section)_
<!--
Describe how you tested this change.
-->
## Reviewer Guidelines
_(fill-in or delete this section)_
<!--
Is there any particular feedback you would / wouldn't like?
Which parts of the code should reviewers focus on?
-->
-->