From f056f5ce1169d286d71eab6c131f3216b4eaf0f0 Mon Sep 17 00:00:00 2001 From: "google-labs-jules[bot]" <161369871+google-labs-jules[bot]@users.noreply.github.com> Date: Thu, 3 Jul 2025 15:40:21 +0000 Subject: [PATCH 1/2] docs: Add section on AI-assisted contributions This commit adds a new section to CONTRIBUTING.md outlining the policy for AI-assisted contributions. It emphasizes that the human PR author is responsible for understanding, vetting, and discussing the code, and that failure to do so may result in the PR not being reviewed. --- CONTRIBUTING.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 324801cfc3..c8cc4fd409 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -318,6 +318,16 @@ Not breaking changes: * Changing internal details, such as renaming an internal file. * Changing a rule to a macro. +## AI-assisted Contributions + +Contributions assisted by AI tools are welcome. However, the human author submitting the Pull Request (PR) bears full responsibility for the contributed code. This means: + +* **Understanding the Code:** You must be able to explain what the code does and why it's implemented that way. +* **Vetting for Correctness and Functionality:** You are responsible for thoroughly testing and verifying that the code is correct, functional, and meets all project requirements and standards. +* **Cogent Discussion:** You must be able to discuss the code, its implications, and any trade-offs made during its development, just as if you had written it entirely yourself. + +If the human PR author cannot fulfill these responsibilities, the `rules_python` maintainers will not spend time reviewing or merging the PR. The goal is to ensure that all contributions, regardless of their origin, maintain the quality and integrity of the project and do not place an undue burden on maintainers. + ## FAQ ### Installation errors when during `git commit` From ad1c6ab346e8e4d007f591c818d1acd16e1f5404 Mon Sep 17 00:00:00 2001 From: Richard Levasseur Date: Thu, 3 Jul 2025 08:46:07 -0700 Subject: [PATCH 2/2] wrap and slightly rephrase --- CONTRIBUTING.md | 23 ++++++++++++++++------- 1 file changed, 16 insertions(+), 7 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index c8cc4fd409..8f985c551b 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -320,13 +320,22 @@ Not breaking changes: ## AI-assisted Contributions -Contributions assisted by AI tools are welcome. However, the human author submitting the Pull Request (PR) bears full responsibility for the contributed code. This means: - -* **Understanding the Code:** You must be able to explain what the code does and why it's implemented that way. -* **Vetting for Correctness and Functionality:** You are responsible for thoroughly testing and verifying that the code is correct, functional, and meets all project requirements and standards. -* **Cogent Discussion:** You must be able to discuss the code, its implications, and any trade-offs made during its development, just as if you had written it entirely yourself. - -If the human PR author cannot fulfill these responsibilities, the `rules_python` maintainers will not spend time reviewing or merging the PR. The goal is to ensure that all contributions, regardless of their origin, maintain the quality and integrity of the project and do not place an undue burden on maintainers. +Contributions assisted by AI tools are allowed. However, the human author +submitting the pull request is responsible for the contributed code as if they +had written it entirely themselves. This means: + +* **Understanding the code:** You must be able to explain what the code does + and why it's implemented that way. This includes discussing its + implications, and any trade-offs made during its development, just as if you + had written it entirely yourself. +* **Vetting the correctness and functionality:** You are responsible for + thoroughly testing and verifying that the code is correct, functional, and + meets all project requirements and standards. + +If the human PR author cannot fulfill these responsibilities, the `rules_python` +maintainers will not spend time reviewing or merging the PR. The goal is to +ensure that all contributions, regardless of their origin, maintain the quality +and integrity of the project and do not place an undue burden on maintainers. ## FAQ