This is an automated email from the ASF dual-hosted git repository.

slachiewicz pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-site-plugin.git


The following commit(s) were added to refs/heads/master by this push:
     new eeba50c  Add PR template
eeba50c is described below

commit eeba50cf6854c9cca709ae47a626d57d924e463e
Author: Slawomir Jaranowski <s.jaranow...@gmail.com>
AuthorDate: Fri Nov 19 18:18:56 2021 +0100

    Add PR template
---
 .github/pull_request_template.md | 29 +++++++++++++++++++++++++++++
 1 file changed, 29 insertions(+)

diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
new file mode 100644
index 0000000..6981adf
--- /dev/null
+++ b/.github/pull_request_template.md
@@ -0,0 +1,29 @@
+Following this checklist to help us incorporate your 
+contribution quickly and easily:
+
+ - [ ] Make sure there is a [JIRA 
issue](https://issues.apache.org/jira/browse/MSITE) filed 
+       for the change (usually before you start working on it).  Trivial 
changes like typos do not 
+       require a JIRA issue.  Your pull request should address just this 
issue, without 
+       pulling in other changes.
+ - [ ] Each commit in the pull request should have a meaningful subject line 
and body.
+ - [ ] Format the pull request title like `[MSITE-XXX] - Fixes bug in 
ApproximateQuantiles`,
+       where you replace `MSITE-XXX` with the appropriate JIRA issue. Best 
practice
+       is to use the JIRA issue title in the pull request title and in the 
first line of the 
+       commit message.
+ - [ ] Write a pull request description that is detailed enough to understand 
what the pull request does, how, and why.
+ - [ ] Run `mvn clean verify` to make sure basic checks pass. A more thorough 
check will 
+       be performed on your pull request automatically.
+ - [ ] You have run the integration tests successfully (`mvn -Prun-its clean 
verify`).
+
+If your pull request is about ~20 lines of code you don't need to sign an
+[Individual Contributor License 
Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure
+please ask on the developers list.
+
+To make clear that you license your contribution under 
+the [Apache License Version 2.0, January 
2004](http://www.apache.org/licenses/LICENSE-2.0)
+you have to acknowledge this by using the following check-box.
+
+ - [ ] I hereby declare this contribution to be licenced under the [Apache 
License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
+
+ - [ ] In any other case, please file an [Apache Individual Contributor 
License Agreement](https://www.apache.org/licenses/icla.pdf).
+

Reply via email to