meta: add a root-level AGENTS.md - #65493
Conversation
We're seeing a number of repeated mistakes in AI-generated contributions, including agents using `Signed-off-by`, creating what appear to be unsupervised PRs, appearing to respond to comments without human oversight, etc. Having an AGENTS.md file with specific instructions to the agent on what to avoid should help. Signed-off-by: James M Snell <jasnell@gmail.com>
ed9ce39 to
37e80dd
Compare
|
There is an ealier PR for AGENTS.md: #65463 |
|
|
||
| ### Requirements | ||
|
|
||
| - All commits must be signed off by the human user using `Signed-off-by: <your name> (<your email>)` as an attestation to the [Developer Certificate of Origin](https://developercertificate.org/). |
There was a problem hiding this comment.
| - All commits must be signed off by the human user using `Signed-off-by: <your name> (<your email>)` as an attestation to the [Developer Certificate of Origin](https://developercertificate.org/). | |
| - All commits must be signed off by the human user using `Signed-off-by: <your name> (<your email>)` as an attestation to the [Developer Certificate of Origin](https://developercertificate.org/). As an AI agent, you are forbidden from leaving this trailer yourself. |
I'm aware we say it later, but it never hurts to be explicit
There was a problem hiding this comment.
As the comment says, it already says this later on:
AI agents must not:
- Sign off commits using
Signed-off-by: <agent name>orCo-authored-by: <agent name>
Given that this file is intended to be read by a machine, repeating the instruction is probably unnecessary.
MikeMcC399
left a comment
There was a problem hiding this comment.
Good to see the experience of receiving and responding to AI-assisted / -generated PRs has resulted in a proposal for explicit coverage in an AGENTS.md directive!
#62612 disabled linting for AGENTS.md. Consider re-enabling, then re-formatting and responding to linting findings. I noticed because #65463 from @BethGriggs had done this.
| Automated interactions that violate these rules may result in: | ||
| - Immediate closure of pull requests without review | ||
| - Blocking of the automation tool from further interaction with the project | ||
| - Blocking of the tool's owner or organization from contributing |
There was a problem hiding this comment.
With my moderation hat on, I'm not sure this is enforceable. We can block accounts only AFAIK.
We're seeing a number of repeated mistakes in AI-generated contributions, including agents using
Signed-off-by, creating what appear to be unsupervised PRs, appearing to respond to comments without human oversight, etc. Having an AGENTS.md file with specific instructions to the agent on what to avoid should help.