From 406c1d7d306472d12cae69d345c9e28b18815cdc Mon Sep 17 00:00:00 2001
From: weiqingy <yangweiqing001@gmail.com>
Date: Mon, 27 Jul 2026 22:12:32 -0700
Subject: [PATCH] [infra] Surface the ASF generative-AI disclosure in the PR
 template

---
 .github/PULL_REQUEST_TEMPLATE.md | 9 +++++++++
 AGENTS.md                        | 2 +-
 2 files changed, 10 insertions(+), 1 deletion(-)

diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index 31fd92ba6..ec30f12ee 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -25,3 +25,12 @@ Linked issue: #xxx
 - [ ] `doc-needed` <!-- Your PR changes impact docs -->
 - [ ] `doc-not-needed` <!-- Your PR changes do not impact docs -->
 - [ ] `doc-included` <!-- Your PR already contains the necessary documentation updates -->
+
+### Was this patch authored or co-authored using generative AI tooling?
+
+<!-- Do not remove this section. Check the proper box only. -->
+
+- [ ] Yes
+- [ ] No
+
+If yes, include a `Generated-by: <tool name and version>` line in this description. See the [ASF generative tooling guidance](https://www.apache.org/legal/generative-tooling.html).
diff --git a/AGENTS.md b/AGENTS.md
index d536f8d77..4eae3208b 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -25,7 +25,7 @@ Java tests use JUnit 5 with AssertJ and Mockito. Python tests use pytest; integr
 
 ## Commit & Pull Request Guidelines
 
-Use concise subjects with bracketed components, matching existing history, such as `[python] Admit bytes in memory values` or `[api][java] Add event constants`. For nontrivial behavior changes, open or link a GitHub issue before the PR. PR titles should include relevant components like `[api]`, `[runtime]`, `[java]`, `[python]`, or `[hotfix]`; describe the change, test evidence, and any compatibility impact.
+Use concise subjects with bracketed components, matching existing history, such as `[python] Admit bytes in memory values` or `[api][java] Add event constants`. For nontrivial behavior changes, open or link a GitHub issue before the PR. PR titles should include relevant components like `[api]`, `[runtime]`, `[java]`, `[python]`, or `[hotfix]`; describe the change, test evidence, and any compatibility impact. Answer the PR template's generative-AI question, and when such tooling was used, include a `Generated-by: <tool name and version>` line in the PR description, per the [ASF generative tooling guidance](https://www.apache.org/legal/generative-tooling.html).
 
 ## Code Review