djpbessems
/
ContainerImage.Pinniped
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
ContainerImage.Pinniped/.github/pull_request_template.md

42 lines
1.2 KiB
Markdown
Raw Normal View History

Iterate on pull request template. - Moves the "front matter" to a Markdown comment so you don't necessarily have to delete it. - Reduces a little bit of boilerplate (this is a bit subjective). - Tweaks some formatting (also subjective). - Describe what happens when you use "Fixes [...]". - Tweak the release note block so it should be easier to parse out automatically (using the same syntax as Kubernetes). Signed-off-by: Matt Moyer <moyerm@vmware.com>
2020-10-02 21:01:28 +00:00
<!--
First draft of a PR template file.
2020-09-16 15:56:18 +00:00
Thank you for submitting a pull request for Pinniped!
Rename the CoC and contributor guide to the names GitHub recognizes. These special names are recognized by GitHub, for example on https://github.com/vmware-tanzu/pinniped/community. Signed-off-by: Matt Moyer <moyerm@vmware.com>
2020-10-02 20:00:23 +00:00
Before submitting, please see the guidelines in CONTRIBUTING.md in this repo.
First draft of a PR template file.
2020-09-16 15:56:18 +00:00
Small edits to PR template file
2020-09-16 16:06:36 +00:00
Please note that a project maintainer will need to review and provide an
initial approval on the PR to cause CI tests to automatically start.
Also note that if you push additional commits to the PR, those commits
will need another initial approval before CI will pick them up.
First draft of a PR template file.
2020-09-16 15:56:18 +00:00
Small edits to PR template file
2020-09-16 16:06:36 +00:00
Reminder: Did you remember to run all the linter, unit tests, and integration tests
Rename the CoC and contributor guide to the names GitHub recognizes. These special names are recognized by GitHub, for example on https://github.com/vmware-tanzu/pinniped/community. Signed-off-by: Matt Moyer <moyerm@vmware.com>
2020-10-02 20:00:23 +00:00
described in CONTRIBUTING.md on your branch before submitting this PR?
First draft of a PR template file.
2020-09-16 15:56:18 +00:00
Below is a template to help you describe your PR.
Iterate on pull request template. - Moves the "front matter" to a Markdown comment so you don't necessarily have to delete it. - Reduces a little bit of boilerplate (this is a bit subjective). - Tweaks some formatting (also subjective). - Describe what happens when you use "Fixes [...]". - Tweak the release note block so it should be easier to parse out automatically (using the same syntax as Kubernetes). Signed-off-by: Matt Moyer <moyerm@vmware.com>
2020-10-02 21:01:28 +00:00
-->
First draft of a PR template file.
2020-09-16 15:56:18 +00:00
Iterate on pull request template. - Moves the "front matter" to a Markdown comment so you don't necessarily have to delete it. - Reduces a little bit of boilerplate (this is a bit subjective). - Tweaks some formatting (also subjective). - Describe what happens when you use "Fixes [...]". - Tweak the release note block so it should be easier to parse out automatically (using the same syntax as Kubernetes). Signed-off-by: Matt Moyer <moyerm@vmware.com>
2020-10-02 21:01:28 +00:00
<!--
Provide a summary of your change. Feel free to use paragraphs or a bulleted list, for example:
First draft of a PR template file.
2020-09-16 15:56:18 +00:00
Iterate on pull request template. - Moves the "front matter" to a Markdown comment so you don't necessarily have to delete it. - Reduces a little bit of boilerplate (this is a bit subjective). - Tweaks some formatting (also subjective). - Describe what happens when you use "Fixes [...]". - Tweak the release note block so it should be easier to parse out automatically (using the same syntax as Kubernetes). Signed-off-by: Matt Moyer <moyerm@vmware.com>
2020-10-02 21:01:28 +00:00
- Improves performance by 10,000%.
- Fixes all bugs.
- Boils the oceans.
First draft of a PR template file.
2020-09-16 15:56:18 +00:00
Iterate on pull request template. - Moves the "front matter" to a Markdown comment so you don't necessarily have to delete it. - Reduces a little bit of boilerplate (this is a bit subjective). - Tweaks some formatting (also subjective). - Describe what happens when you use "Fixes [...]". - Tweak the release note block so it should be easier to parse out automatically (using the same syntax as Kubernetes). Signed-off-by: Matt Moyer <moyerm@vmware.com>
2020-10-02 21:01:28 +00:00
-->
First draft of a PR template file.
2020-09-16 15:56:18 +00:00
Iterate on pull request template. - Moves the "front matter" to a Markdown comment so you don't necessarily have to delete it. - Reduces a little bit of boilerplate (this is a bit subjective). - Tweaks some formatting (also subjective). - Describe what happens when you use "Fixes [...]". - Tweak the release note block so it should be easier to parse out automatically (using the same syntax as Kubernetes). Signed-off-by: Matt Moyer <moyerm@vmware.com>
2020-10-02 21:01:28 +00:00
<!--
Does this PR fix one or more reported issues?
If yes, use `Fixes #<issue number>` to automatically close the fixed issue(s) when the PR is merged.
-->
First draft of a PR template file.
2020-09-16 15:56:18 +00:00
Iterate on pull request template. - Moves the "front matter" to a Markdown comment so you don't necessarily have to delete it. - Reduces a little bit of boilerplate (this is a bit subjective). - Tweaks some formatting (also subjective). - Describe what happens when you use "Fixes [...]". - Tweak the release note block so it should be easier to parse out automatically (using the same syntax as Kubernetes). Signed-off-by: Matt Moyer <moyerm@vmware.com>
2020-10-02 21:01:28 +00:00
**Release note**:
<!--
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.
-->
```release-note
Small edits to PR template file
2020-09-16 16:06:36 +00:00
First draft of a PR template file.
2020-09-16 15:56:18 +00:00
```