yihua opened a new pull request, #19134:
URL: https://github.com/apache/hudi/pull/19134

   ### Describe the issue this Pull Request addresses
   
   Commits should not credit AI assistants as co-authors. This PR adds an 
automated guard so that PR commits carrying a `Co-authored-by: Claude ...` (or 
any anthropic.com) trailer are caught in CI instead of relying on reviewers to 
spot them.
   
   ### Summary and Changelog
   
   - Adds a new GitHub Actions workflow `commit_coauthor_validation.yml` with a 
`validate-commit-coauthor` job that runs on `pull_request` events targeting 
`master` and `branch-0.x`. It lists all commits of the PR via the GitHub API 
and fails if any commit message contains a `Co-authored-by:` trailer naming 
Claude or an anthropic.com address, printing the offending commit SHAs and how 
to fix them (amend/rebase to drop the trailer).
   - Registers `validate-commit-coauthor` under `required_status_checks` in 
`.asf.yaml` so the check is required on `master`.
   
   ### Impact
   
   CI/process only; no code or user-facing changes. PRs with a Claude co-author 
trailer in any commit will fail the new required check until the trailer is 
removed.
   
   ### Risk Level
   
   low. The check is read-only (GitHub API listing of PR commits) and the regex 
was verified against positive cases (`Co-authored-by: Claude 
<[email protected]>`, model-specific variants) and negative cases (human 
co-authors, mentions of "claude"/"anthropic.com" in the commit body outside a 
trailer).
   
   ### Documentation Update
   
   none
   
   ### Contributor's checklist
   
   - [x] Read through [contributor's 
guide](https://hudi.apache.org/contribute/how-to-contribute)
   - [x] Enough context is provided in the sections above
   - [x] Adequate tests were added if applicable
   


-- 
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