(maven-wrapper) branch master updated: Simplify GH PR template boilerplate

[sj...@apache.org]

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-wrapper.git


The following commit(s) were added to refs/heads/master by this push:
     new 24915d7  Simplify GH PR template boilerplate
24915d7 is described below

commit 24915d789fc9b6e6316c3d6806ca94782fc2c713
Author: Slawomir Jaranowski <s....@gmail.com>
AuthorDate: Fri Oct 2 20:20:46 2026 +0200

    Simplify GH PR template boilerplate
    
    [ci skip]
    
    Co-Authored-By: Claude Opus 5.5 <no...@anthropic.com>
---
 .github/pull_request_template.md | 24 ++++++------------------
 1 file changed, 6 insertions(+), 18 deletions(-)

diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index 0456e30..63948e0 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -1,23 +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.
-- [ ] You have run the integration tests successfully (`mvn -Prun-its verify`).
+<!-- 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).