spuru9 opened a new pull request, #1133:
URL: https://github.com/apache/flink-kubernetes-operator/pull/1133

   ## What is the purpose of the change
   
   This pull request adds a "Was generative AI tooling used to co-author this 
PR?" section to the repository's pull request template, mirroring the section 
already present in `apache/flink`.
   
   This is a follow-up to 
[FLINK-39477](https://issues.apache.org/jira/browse/FLINK-39477), which adopted 
AI-assisted contribution guidelines for the main Flink repository. That ticket 
was closed with a note that other Flink-project owned repositories should 
create related follow-ups — this PR is the follow-up for the Kubernetes 
Operator.
   
   ## Brief change log
   
     - Append the "Was generative AI tooling used to co-author this PR?" 
section to `.github/PULL_REQUEST_TEMPLATE.md`, including the disclosure 
checkbox, the `Generated-by:` line, and a link to the ASF Generative Tooling 
Guidance.
     - Omit the `AGENTS.md` reference from `apache/flink`'s wording, since no 
such file exists in this repository.
   
   ## Verifying this change
   
   This change is a trivial rework / code cleanup without any test coverage 
(PR-template / documentation only).
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): no
     - The public API, i.e., is any changes to the `CustomResourceDescriptors`: 
no
     - Core observer or reconciler logic that is regularly executed: no
   
   ## Documentation
   
     - Does this pull request introduce a new feature? no
     - If yes, how is the feature documented? not applicable
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes (please specify the tool below)
   
   Generated-by: Claude Code (Claude Opus 4.8)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to