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 6168a2a8 [infra] Include model in AI provenance (#993)
6168a2a8 is described below
commit 6168a2a87c35a0196f73bb682bb39fe7bb79f860
Author: Wenjin Xie <[email protected]>
AuthorDate: Tue Aug 11 11:20:11 2026 +0800
[infra] Include model in AI provenance (#993)
Generated-by: Codex 0.144.5 (GPT-5)
---
.github/PULL_REQUEST_TEMPLATE.md | 2 +-
AGENTS.md | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index e4b8cb11..babbbe7d 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -33,4 +33,4 @@ Linked issue: #xxx
- [ ] 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).
+If yes, include a `Generated-by: <tool name and version> (<model name and
version>)` line, for example `Generated-by: Claude Code 2.1.226 (Claude Opus
4.6)`, in the commit message so it reaches Git history. Repeat the same line
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 d308d019..cfe000e0 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. Answer the PR template's generative-AI question, and
when such tooling was used, [...]
+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
