weiguoqiang/cert-manager
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

update PR template to be simpler and mention allowing edits

Browse Source 
Signed-off-by: Ashley Davis <ashley.davis@jetstack.io>
This commit is contained in:
Ashley Davis 2022-01-24 15:29:48 +00:00
parent 53ef87a526
commit a5fcd70b76
No known key found for this signature in database
GPG Key ID: DD14CC017E32BEB1
1 changed files with 23 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

35
.github/PULL_REQUEST_TEMPLATE.md vendored
View File

@ -1,20 +1,31 @@
<!-- Thanks for sending a pull request! Here are some tips for you:
1. If this is your first time, read our contributor guidelines https://git.k8s.io/community/contributors/guide#your-first-contribution and developer guide https://git.k8s.io/community/contributors/devel/development.md#development-guide
2. If you want *faster* PR reviews, read how: https://git.k8s.io/community/contributors/guide/pull-requests.md#best-practices-for-faster-reviews
3. Follow the instructions for writing a release note: https://git.k8s.io/community/contributors/guide/release-notes.md
4. If the PR is unfinished, see how to mark it: https://git.k8s.io/community/contributors/guide/pull-requests.md#marking-unfinished-pull-requests
<!--
Thanks for opening a pull request! Here are some tips to get everything merged smoothly:
1. Read our contributor guidelines: https://cert-manager.io/docs/contributing/
2. Make sure your commits are signed off: https://cert-manager.io/docs/contributing/sign-off/
3. If the PR is unfinished, raise it as a draft or prefix the title with "WIP:" so it's clear to everyone.
4. Be sure to allow edits from maintainers so it's easier for us to help: https://help.github.com/en/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork
-->
**What this PR does / why we need it**:
## Pull Request Motivation
**Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #
<!-- Explain the motivation behind this PR. If there's a related issue or PR, link to it here! -->
**Special notes for your reviewer**:
## Release Note
<!--
Should we mention this PR in release notes? If so, replace "NONE" with a line of text explaining what changed!
For more details, see: https://git.k8s.io/community/contributors/guide/release-notes.md
**Release note**:
<!-- Steps to write your release note:
1. Use the release-note-* labels to set the release note state (if you have access)
2. Enter your extended release note in the below block; leaving it blank means using the PR title as the release note. If no release note is required, just write `NONE`.
-->
```release-note
NONE
```