Skip to content

Commit 21b1954

Browse files
authored
Merge pull request #729 from python-attrs/more-slop
2 parents 304e370 + 4ec1725 commit 21b1954

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

.github/AI_POLICY.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ As the makers of software that is used by millions of people worldwide and with
4141
No matter what LLM vendors or boosters on LinkedIn tell you, we have to manually review every change before merging, because it's **our responsibility** to keep the project stable.
4242

4343
Please understand that by opening low-quality pull requests you're not helping anyone.
44-
Worse, you're [poisoning the open source ecosystem](https://lwn.net/SubscriberLink/1058266/cfe99725c2855d66/) that was precarious even before the arrival of LLM tools.
44+
Worse, you're [poisoning the open source ecosystem](https://lwn.net/Articles/1058266/) that was precarious even before the arrival of LLM tools.
4545
Having to wade through plausible-looking-but-low-quality pull requests and trying to determine which ones are legit is extremely demoralizing and has already burned out many good maintainers.
4646

4747
Put bluntly, we have no time or interest to become part of your vibe coding loop where you drop LLM slop at our door, we spend time and energy to review it, and you just feed it back into the LLM for another iteration.
@@ -65,7 +65,7 @@ In practice, this means:
6565

6666
- Accounts that exercise bot-like behavior – like automated mass pull requests – will be permanently banned, whether they belong to a human or not.
6767

68-
- Do **not** post LLM-generated review comments unless you agree with them.
69-
Do **not** post summaries unless you take responsibility for 100% of their content.
68+
- Do **not** post LLM-generated review comments -- we can prompt LLMs ourselves should we desire their wisdom.
69+
Do **not** post summaries unless you've fact-checked them and take responsibility for 100% of their content.
7070
Remember that *all* LLM output *looks* **plausible**.
71-
When using these tools, it's **your** responsibility to ensure that it's also **correct**.
71+
When using these tools, it's **your** responsibility to ensure that it's also **correct** and has a reasonable signal-to-noise ratio.

0 commit comments

Comments
 (0)