This is an automated email from the ASF dual-hosted git repository.
ggregory pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/commons-release-plugin.git
The following commit(s) were added to refs/heads/master by this push:
new 330176f Update the GitHub pull request template for AI
330176f is described below
commit 330176fee9f09fd3a213a5b2573922745ace1c8d
Author: Gary D. Gregory <garydgreg...@gmail.com>
AuthorDate: Sun Jul 20 13:32:05 2025 -0400
Update the GitHub pull request template for AI
Better grammar
---
.github/pull_request_template.md | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index d126a97..7578b4d 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -7,7 +7,7 @@
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
- http://www.apache.org/licenses/LICENSE-2.0
+ https://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
@@ -22,7 +22,9 @@ Thanks for your contribution to [Apache
Commons](https://commons.apache.org/)! Y
Before you push a pull request, review this list:
- [ ] Read the [contribution guidelines](CONTRIBUTING.md) for this project.
+- [ ] Read the [ASF Generative Tooling
Guidance](https://www.apache.org/legal/generative-tooling.html) if you use
Artificial Intelligence (AI).
+- [ ] I used AI to create any part of, or all of, this pull request.
- [ ] Run a successful build using the default
[Maven](https://maven.apache.org/) goal with `mvn`; that's `mvn` on the command
line by itself.
-- [ ] 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.
+- [ ] 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 it is a best-practice.
- [ ] 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.
+- [ ] Each commit in the pull request should have a meaningful subject line
and body. Note that a maintainer may squash commits during the merge process.
