Stricter Agents w/ PR and Issue policy#1894
Merged
Merged
Conversation
|
coverage: 93.067%. remained the same — agents-post-pycon2026 into master |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
After Paolo Melchiorre's talk AI-Assisted Contributions and Maintainer Load at PyCon, I realized that the restrictions on AI PRs and issues need to be spelled out better.
AI-aided Human contributions are still welcome. Even all AI written if they work and are valuable can be considered. But anything that breaks code or has any agent pushback will result in the banning of the user.
Too many other projects have been severely hurt in the past year by lack of such a policy.