From 207549dc7db5d46a81ee09224a50d99a7e462f50 Mon Sep 17 00:00:00 2001 From: "Jeong, YunWon" <69878+youknowone@users.noreply.github.com> Date: Tue, 11 Aug 2026 21:49:18 +0900 Subject: [PATCH] Remove allowlist policy in AI-assisted pull request guidelines Updated guidelines for AI-assisted pull requests, clarifying that they may be closed at maintainers' discretion and outlining reasons for potential closure. --- AI_POLICY.md | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/AI_POLICY.md b/AI_POLICY.md index 34a5741..bac86a0 100644 --- a/AI_POLICY.md +++ b/AI_POLICY.md @@ -13,11 +13,14 @@ The RustPython project has the following rules for AI usage: messages. For commit messages, use the `Assisted-by` trailer (see below for the required format). - - *Pull requests created in any way by AI can only be for accepted issues.* - Drive-by pull requests that do not reference an accepted issue will be - closed. If AI isn't disclosed but a maintainer suspects its use, the PR - will be closed. If you want to share code for a non-accepted issue, open - a discussion or attach it to an existing discussion. + - *Pull requests created in any way by AI may be closed at the maintainers' discretion.* + They may be closed for a variety of reasons at any time. Reasons may include, but are not limited to: + the issue being considered unsuitable for AI-assisted contribution; + the generated code appearing insufficiently reviewed by the contributor and therefore not ready for maintainer review; + suspected use of AI that was not disclosed; or other practical maintenance considerations. + + If you believe a pull request was closed by mistake, please leave a comment explaining why. + A decision to close an individual pull request applies only to that pull request and should not be understood as a judgment about, or restriction on, the contributor. - *Pull requests created by AI must have been fully verified with human use.* AI must not create hypothetically correct code that hasn't been tested.