[blocked] Add LLM guidance, based on the new rl/r policy - #2835
Conversation
| ### Rules | ||
|
|
||
| We expect everyone to follow the new policy, not just authors. | ||
| That means it is **your responsibility** to check whether an `ai-assisted` PR touches an area that's disallowed by the policy. |
There was a problem hiding this comment.
would it make sense to have a bot that checks this automatically? like, that sends a "hey, this PR is labeled as ai-assisted and is editing the clippy subtree. be aware that subtrees may have their own LLM policy" or something similar.
(sorry, this is not super actionable for you right now :/)
|
Thanks for the PR. If you have write access, feel free to merge this PR if it does not need reviews. You can request a review using |
| ### When opening a PR | ||
|
|
||
| Disclose your use of LLMs, following the disclosure guidelines below. | ||
| Write the disclosure yourself. | ||
| You may use an LLM to privately review a disclosure you have written, but not to draft or rewrite it. | ||
|
|
||
| **Write your own PR description and comments**. | ||
| We want to hear from you, not from your agent. | ||
| LLM-created PR descriptions are banned. | ||
| LLM-created Github comments are banned. |
There was a problem hiding this comment.
Up in the "reviewing llm code", it is said
## Reviewing LLM-created code
First, add the new `ai-assisted` label to the PR.
can we include this prose here additionally/instead? Adding an ai-assisted label yourself feels like part of disclosure to me.
There was a problem hiding this comment.
this is mildly annoying for people who aren’t in the org because they have to go through triagebot to change labels. i think disclosure in the PR description is enough, maybe we can have triagebot do something fancy with the checkboxes idk.
This is blocked until rust-lang/rust-forge#1040 merges.
Note that I also link to this in the blog post (
https://github.com/rust-lang/blog.rust-lang.org/pull/1897), so it needs to be merged before that post.