mirror of
https://github.com/k3s-io/k3s.git
synced 2024-06-07 19:41:36 +00:00
Add user-facing change section to PR template
Signed-off-by: Brad Davidson <brad.davidson@rancher.com>
This commit is contained in:
parent
a5cff7e143
commit
4a6e87e5a2
10
.github/PULL_REQUEST_TEMPLATE.md
vendored
10
.github/PULL_REQUEST_TEMPLATE.md
vendored
@ -17,7 +17,15 @@
|
||||
|
||||
<!-- Link any related issues, pull-requests, or commit hashes that are relevant to this pull request. If you are opening a PR without a corresponding issue please consider creating one first, at https://github.com/rancher/k3s/issues . A functional example will greatly help QA with verifying/reproducing a bug or testing new features. -->
|
||||
|
||||
#### User-Facing Change ####
|
||||
<!--
|
||||
Does this PR introduce a user-facing change? If no, just write "NONE" in the release-note block below.
|
||||
If the PR requires additional action from users switching to the new release, include the string "action required".
|
||||
-->
|
||||
```release-note
|
||||
|
||||
```
|
||||
|
||||
#### Further Comments ####
|
||||
|
||||
<!-- If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc... -->
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user