maven-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From eolive...@apache.org
Subject [maven-javadoc-plugin] branch master updated: Add GitHub pull requests template (copied from Maven Enforcer plugin)
Date Wed, 13 Feb 2019 21:30:15 GMT
This is an automated email from the ASF dual-hosted git repository.

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


The following commit(s) were added to refs/heads/master by this push:
     new 9df315c  Add GitHub pull requests template (copied from Maven Enforcer plugin)
9df315c is described below

commit 9df315c1097a3db3b6162a1d3c830bbcf674cb98
Author: Enrico Olivelli <eolivelli@apache.org>
AuthorDate: Wed Feb 13 22:30:01 2019 +0100

    Add GitHub pull requests template (copied from Maven Enforcer plugin)
---
 .github/pull_request_template.md | 28 ++++++++++++++++++++++++++++
 1 file changed, 28 insertions(+)

diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
new file mode 100644
index 0000000..df2c7b7
--- /dev/null
+++ b/.github/pull_request_template.md
@@ -0,0 +1,28 @@
+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/MJAVADOC)
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 `[MJAVADOC-XXX] - Fixes bug in ApproximateQuantiles`,
+       where you replace `MJAVADOC-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.
+
+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).
+


Mime
View raw message