From d8cbbc414e4f695521777e42a6e1dfa9fd099f95 Mon Sep 17 00:00:00 2001 From: Maxime Guyot <Miouge1@users.noreply.github.com> Date: Thu, 11 Apr 2019 12:04:14 +0200 Subject: [PATCH] Add a PR template (#4491) --- .github/PULL_REQUEST_TEMPLATE.md | 44 ++++++++++++++++++++++++++++++++ 1 file changed, 44 insertions(+) create mode 100644 .github/PULL_REQUEST_TEMPLATE.md diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md new file mode 100644 index 000000000..c99222977 --- /dev/null +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -0,0 +1,44 @@ +<!-- Thanks for sending a pull request! Here are some tips for you: + +1. If this is your first time, please 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. Please label this pull request according to what type of issue you are addressing, especially if this is a release targeted pull request. For reference on required PR/issue labels, read here: +https://git.k8s.io/community/contributors/devel/release.md#issue-kind-label +3. Ensure you have added or ran the appropriate tests for your PR: https://git.k8s.io/community/contributors/devel/testing.md +4. If you want *faster* PR reviews, read how: https://git.k8s.io/community/contributors/guide/pull-requests.md#best-practices-for-faster-reviews +5. Follow the instructions for writing a release note: https://git.k8s.io/community/contributors/guide/release-notes.md +6. 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 ` /kind <>` line, hit enter to put that in a new line, and remove leading whitespaces from that line: +> +> /kind api-change +> /kind bug +> /kind cleanup +> /kind design +> /kind documentation +> /kind failing-test +> /kind feature +> /kind flake + +**What this PR does / why we need it**: + +**Which issue(s) this PR fixes**: +<!-- +*Automatically closes linked issue when PR is merged. +Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`. +_If PR is about `failing-tests or flakes`, please post the related issues/tests in a comment and do not use `Fixes`_* +--> +Fixes # + +**Special notes for your reviewer**: + +**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". +--> +```release-note + +``` -- GitLab