You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by sj...@apache.org on 2026/10/02 18:20:00 UTC
(maven-plugin-testing) branch master updated: Simplify GH PR template boilerplate
This is an automated email from the ASF dual-hosted git repository.
slawekjaranowski pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-plugin-testing.git
The following commit(s) were added to refs/heads/master by this push:
new f29b08a Simplify GH PR template boilerplate
f29b08a is described below
commit f29b08a489e860053a8ee2d42f8f39f71185b25e
Author: Slawomir Jaranowski <s....@gmail.com>
AuthorDate: Fri Oct 2 20:19:55 2026 +0200
Simplify GH PR template boilerplate
[ci skip]
Co-Authored-By: Claude Opus 5.5 <no...@anthropic.com>
---
.github/pull_request_template.md | 23 ++++++-----------------
1 file changed, 6 insertions(+), 17 deletions(-)
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index a7b7d37..63948e0 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -1,22 +1,11 @@
-Following this checklist to help us incorporate your contribution quickly and easily:
-- [ ] Your pull request should address just one issue, without pulling in other changes.
-- [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
-- [ ] Each commit in the pull request should have a meaningful subject line and body.
- Note that commits might be squashed by a maintainer on merge.
-- [ ] Write unit tests that match behavioral changes, where the tests fail if the changes to the runtime are not applied.
- This may not always be possible but is a best-practice.
-- [ ] Run `mvn verify` to make sure basic checks pass.
- A more thorough check will be performed on your pull request automatically.
+<!-- Add your description here... what, why and how you resolve the issue -->
-
-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.
+the [Apache License Version 2.0, January 2004](https://www.apache.org/licenses/LICENSE-2.0)
+check one of the following:
-- [ ] 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).
+- [ ] I hereby declare this contribution to be licensed under the [Apache License Version 2.0, January 2004](https://www.apache.org/licenses/LICENSE-2.0)
+- [ ] I hereby declare that I have filed an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).