This is an automated email from the ASF dual-hosted git repository.

wenjin272 pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/flink-agents.git


The following commit(s) were added to refs/heads/main by this push:
     new 1ae0d707 [infra] Surface the ASF generative-AI disclosure in the PR 
template (#933)
1ae0d707 is described below

commit 1ae0d707cdfa211d2d41bc9360bff7255492a6e8
Author: Weiqing Yang <[email protected]>
AuthorDate: Wed Aug 5 00:39:10 2026 -0700

    [infra] Surface the ASF generative-AI disclosure in the PR template (#933)
    
    * [infra] Surface the ASF generative-AI disclosure in the PR template
    
    * [infra] Ask for the Generated-by line in the commit message
    
    The ASF guidance asks for the token in the source control commit message so
    future release tooling can pull it into a machine-parsable provenance file.
    This repository enables squash and rebase merges, and squash composes the
    merged body from the source commit messages, so a line present only in the 
PR
    description does not reach Git history on either path.
    
    Ask for the line in the commit message, and keep the PR-description copy for
    reviewer visibility.
    
    Generated-by: Claude Code 2.1.220
---
 .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 31fd92ba..e4b8cb11 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 the commit 
message so it reaches Git history, and repeat it here for reviewer visibility. 
See the [ASF generative tooling 
guidance](https://www.apache.org/legal/generative-tooling.html).
diff --git a/AGENTS.md b/AGENTS.md
index d536f8d7..d308d019 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, [...]
 
 ## Code Review
 

Reply via email to