Skip to content

Tweak AI contribution policy wording #9174

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
tlively merged 1 commit into from
Sep 30, 2026
+9 −9
Merged

Tweak AI contribution policy wording #9174

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 9 additions & 9 deletions Contributing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,15 +9,15 @@ Also, please be sure to read [the README.md](README.md) for this repository.

Contributors may use whatever tools they would like to craft their
contributions, but there must be a human in the loop. Contributors must
self-review and understand all code and documentation updates (with or without
AI tooling) before sending them for review to ensure the correctness, design,
and style meet the standards of the project. The contributor is always the
author and is fully accountable for their contributions. Contributors should be
sufficiently confident that the contribution is high enough quality that asking
for a review is a good use of scarce maintainer time, and they should be able to
answer questions about their work during review. To aid reviewers, contributors
should flag areas they are not confident about that had AI assistance. This can
be done in PR comments, the PR description, or in code comments.
understand their contributions before sending them for review and must ensure
that their correctness, design, and style meet the standards of the project. The
contributor is always the author and is fully accountable for their
contributions. Contributors should be sufficiently confident that the
contribution is high enough quality that asking for a review is a good use of
scarce maintainer time, and they should be able to answer questions about their
work during review. To aid reviewers, contributors should flag areas they are
not confident about that had AI assistance. This can be done in PR comments, the
PR description, or in code comments.

Contributors must attest that the code they submit is their original creation,
regardless of whether AI tooling was used.
Expand Down
Loading