@@ -20,25 +20,16 @@ A contribution that works only narrowly but lowers the quality of the
2020codebase may be declined. The maintainers may not always be able to provide
2121detailed feedback.
2222
23- ## AI-assisted contributions
23+ ## Prevent agent impersonation
2424
25- If AI edits files for you, disclose it in the pull request description and commit
26- metadata. Prefer making the agent identity part of the commit, for example by using
27- an AI author such as ` $agent $version <ai-agent@example.invalid> ` or a co-author via
28- a ` Co-authored-by: <agent-identity> ` trailer .
25+ AI agents communicating through a person's account must identify themselves, for
26+ example in issue or PR descriptions and comments. AI assistance that does not replace
27+ the person as the speaker, such as proofreading or wording polish, does not require
28+ identification .
2929
30- Agents operating through a person's GitHub account must identify themselves. For
31- example, comments posted by an agent should say so directly with phrases like
32- ` AI agent on behalf of <person>: ... ` .
33-
34- Fully AI-generated comments on pull requests or issues must also be disclosed.
35- Undisclosed AI-generated comments may lead to the pull request or issue being closed.
36-
37- AI-assisted proofreading or wording polish does not need disclosure, but it is still
38- courteous to mention it when the AI materially influenced the final text.
39-
40- Automated or "full-auto" AI contributions without a human responsible for reviewing
41- and standing behind the work may be closed.
30+ Attributing AI assistance in commit metadata, for example with a ` Co-authored-by `
31+ trailer, is welcome but not required. Code is reviewed the same way regardless of its
32+ origin.
4233
4334## Fuzzing Test Specific Documentation
4435
0 commit comments