Files
transformers/.github/PULL_REQUEST_TEMPLATE.md
Matt 394b1a0eaa Add big angry code agent warnings! (#44890)
* Add big angry warnings!

* PR template cleanup

* Reformat tip

* Reformat warning

* Writing a little more

* Expanded code agent philosophy

* Expanded code agent philosophy

* Expanded code agent philosophy

* Expanded code agent philosophy

* Expanded code agent philosophy

* Update CONTRIBUTING.md

Co-authored-by: Anton Vlasjuk <73884904+vasqu@users.noreply.github.com>

* Expanded code agent philosophy

* Expanded code agent philosophy

* Clarify guidelines on code agent contributions

Added a section detailing the philosophy regarding code agents and their contributions.

* Refine contribution guidelines in CONTRIBUTING.md

Removed redundant text and clarified guidelines for PR submissions.

* Update .github/PULL_REQUEST_TEMPLATE.md

Co-authored-by: Pedro Cuenca <pedro@huggingface.co>

---------

Co-authored-by: Anton Vlasjuk <73884904+vasqu@users.noreply.github.com>
Co-authored-by: Pedro Cuenca <pedro@huggingface.co>
2026-03-22 18:48:30 +00:00

4.0 KiB

What does this PR do?

Fixes # (issue)

Code Agent Policy

The Transformers repo is currently being overwhelmed by a large number of PRs and issue comments written by code agents. We are currently bottlenecked by our ability to review and respond to them. As a result, we ask that new users do not submit pure code agent PRs at this time. You may use code agents in drafting or to help you diagnose issues. We'd also ask autonomous "OpenClaw"-like agents not to open any PRs or issues for the moment.

PRs that appear to be fully agent-written will probably be closed without review, and we may block users who do this repeatedly or maliciously.

This is a rapidly-evolving situation that's causing significant shockwaves in the open-source community. As a result, this policy is likely to be updated regularly in the near future. For more information, please read CONTRIBUTING.md.

  • I confirm that this is not a pure code agent PR.

Before submitting

  • This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
  • Did you read the contributor guideline, Pull Request section?
  • Was this discussed/approved via a Github issue or the forum? Please add a link to it if that's the case.
  • Did you make sure to update the documentation with your changes? Here are the documentation guidelines, and here are tips on formatting docstrings.
  • Did you write any new necessary tests?

Who can review?

Anyone in the community is free to review the PR once the tests have passed. Feel free to tag members/contributors who may be interested in your PR.