[maven-archetypes] branch master updated: Add pull request template for GitHub

[mt...@apache.org]

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

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


The following commit(s) were added to refs/heads/master by this push:
     new 5d9b21e  Add pull request template for GitHub
5d9b21e is described below

commit 5d9b21e9c7426cd7956fbf52024dfbea78dfa83a
Author: Maarten Mulders <m....@xs4all.nl>
AuthorDate: Fri May 20 20:37:14 2022 +0200

    Add pull request template for GitHub
    
    Does not mention running the integration tests
    as there seem to be none.
---
 .github/pull_request_template.md | 26 ++++++++++++++++++++++++++
 1 file changed, 26 insertions(+)

diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
new file mode 100644
index 0000000..df52056
--- /dev/null
+++ b/.github/pull_request_template.md
@@ -0,0 +1,26 @@
+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/MARCHETYPES) 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 `[MARCHETYPES-XXX] SUMMARY`, where you replace `MARCHETYPES-XXX`
+       and `SUMMARY` 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).