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

etseidl pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/arrow-rs.git


The following commit(s) were added to refs/heads/main by this push:
     new 0e478d8f54 docs: Add guidance for AI assisted submissions to 
CONTRIBUTING.md (#9892)
0e478d8f54 is described below

commit 0e478d8f54b0a18735450b59d80ecc4dce13b012
Author: Ed Seidl <[email protected]>
AuthorDate: Mon May 4 14:16:20 2026 -0700

    docs: Add guidance for AI assisted submissions to CONTRIBUTING.md (#9892)
    
    # Which issue does this PR close?
    
    None
    
    # Rationale for this change
    
    Arrow and Datafusion provide this guidance, it's high time we do as
    well.
    
    # What changes are included in this PR?
    
    Add links to the Arrow and ASF AI policies.
    
    # Are these changes tested?
    
    Docs only
    
    # Are there any user-facing changes?
    
    Only to project documentation
---
 CONTRIBUTING.md | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 83ee468c32..48075c5ef7 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -256,3 +256,21 @@ If sometimes you want to commit without checking, just run 
`git commit` with `--
 ```bash
 git commit --no-verify -m "... commit message ..."
 ```
+
+## AI Generated Submissions
+
+This project follows the guidance for AI generated submissions used by the
+[Arrow 
Project](https://arrow.apache.org/docs/dev/developers/overview.html#ai-generated-code).
+As such, it is expected that you will:
+
+- Only submit a PR if you are able to debug and own the changes yourself - 
review all generated
+  code to understand every detail
+- Match the style and conventions used in the rest of the codebase, including 
PR titles and descriptions
+- Be upfront about AI usage and summarise what was AI-generated
+- If there are parts you don’t fully understand, leave comments on your own PR 
explaining what steps you took to verify correctness
+- Watch for AI’s tendency to generate overly verbose comments, unnecessary 
test cases, and incorrect fixes
+- Break down large PRs into smaller ones to make review easier
+
+It is also important for submitters to be aware of potential copyright issues. 
See the ASF's
+[guidance](https://www.apache.org/legal/generative-tooling.html) on 
AI-generated code for further
+information on licensing considerations.

Reply via email to