github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Adds label prompt and explanation to pull request template 

As the release process no longer requires an issue to be filed with each pull request, we should be treating pull requests as issues for the purposes of triage. This means it is helpful if PR authors add labels right as they open a PR.
pull/58/head
guineveresaenger 2018-10-15 17:20:44 -07:00
parent f6b54f79fb
commit 2baf575fe2
1 changed files with 11 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
.github/PULL_REQUEST_TEMPLATE.md vendored
View File

@ -1,10 +1,18 @@
<!-- Thanks for sending a pull request! Here are some tips for you: <!-- 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 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 2. Please label this pull request according to what type of issue you are fixing, especially if this is a release targeted pull request. For reference on required PR/issue labels, read here:
3. Follow the instructions for writing a release note: https://git.k8s.io/community/contributors/guide/release-notes.md https://github.com/kubernetes/community/blob/master/contributors/devel/release.md#issue-kind-label
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 3. If you want *faster* PR reviews, read how: https://git.k8s.io/community/contributors/guide/pull-requests.md#best-practices-for-faster-reviews
4. Follow the instructions for writing a release note: https://git.k8s.io/community/contributors/guide/release-notes.md
5. If the PR is unfinished, see how to mark it: https://git.k8s.io/community/contributors/guide/pull-requests.md#marking-unfinished-pull-requests
--> -->
**What type of PR is this?**
> Uncomment only one, leave it on its own line:
>
> /kind bug
> /kind feature
**What this PR does / why we need it**: **What this PR does / why we need it**:
**Which issue(s) this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close the issue(s) when PR gets merged)*: **Which issue(s) this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close the issue(s) when PR gets merged)*: