Make AI guidelines more visually noticeable (#5727)

This commit is contained in:
Giovanni 2026-01-04 15:49:04 +08:00 committed by GitHub
parent 5733f0509a
commit 384bebe3d0
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -110,17 +110,19 @@ rules to make the git history more readable and consistent:
Following the widespread availability of large language models and generative AI,
Rizin Organization has received a growing number of changes generated partially or
entirely using such tools. Many of these are completely unusable in our codebase.
While AI tools can help to draft changes, they must not replace human understanding
and proper code modifications.
If you use AI tools to help prepare a code change, you must:
- **Disclose** which AI tools were used and specify what they were used for.
- **Verify** that the code compiles, works and is not copyrighted by somebody else.
- **Avoid** fabricated code, placeholder text, or references to non-existent code.
Changes that appear to be unverified AI output will be closed without response.
Repeated low-quality submissions may result in a ban.
> [!IMPORTANT]
> While AI tools can help to draft changes, **they must NOT replace human understanding
> and proper code modifications**.
>
> If you use AI tools to help prepare a code change, you must:
>
> - **Disclose** which AI tools were used and specify what they were used for.
> - **Verify** that the code compiles, works and is not copyrighted by somebody else.
> - **Avoid** fabricated code, placeholder text, or references to non-existent code.
>
> Changes that appear to be unverified AI output will be closed without response.
> Repeated low-quality submissions may result in a ban.
We align with similar policies adopted by other major open-source projects, which have
described the flood of unverified AI-generated code changes as disruptive, counterproductive,