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-jelly.git
The following commit(s) were added to refs/heads/master by this push:
new 10109a18 Ask for details on AI usage in creating a pull request
10109a18 is described below
commit 10109a1802e9d43857d8ca74233675cd82df0f7c
Author: Gary Gregory <[email protected]>
AuthorDate: Fri Dec 5 17:03:02 2025 -0500
Ask for details on AI usage in creating a pull request
---
.github/pull_request_template.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index 4cbe168c..9ff35c83 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -23,7 +23,7 @@ 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.
+- [ ] I used AI to create any part of, or all of, this pull request. Which AI
tool was used to create this pull request, and to what extent did it contribute?
- [ ] 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 it is a best practice.
- [ ] Write a pull request description that is detailed enough to understand
what the pull request does, how, and why.
