Note on AI submitted PRs, commits, discussions and security reports

[mgogoulos]

This project has been receiving a big number of AI produced content the last few months and this affects the small team that maintains and cares about the project in a negative way. In some cases it's clearly a waste of time to try to understand what the content is about, and it's clearly coming from automated tools that the submitter has not even bothered to check, review, or at least read one time.

This is a trending issue for any single project in Github apparently and I want to note that we're very aware of it and we're trying to find solutions. At this moment I have to say that immediately rejecting any AI contribution that hasn't been curated at all by the submitter seems like a positive thing for the project. We should come up with guidelines on how to handle this topic as it affects quality of the project and developer experience in a negative way. Open to suggestions!

[undulanti]

I would do exactly as you suggest: immediately reject any AI contribution that hasn't been curated at all by the submitter. If they genuinely have something valuable to add, they will almost certainly try again in a more thoughtful way.

Presumably GitHub will itself start to put guardrails on all this, as it's impacting so many projects, so perhaps wait it out and see what they do before spending time on a project-specific policy.

Your value to the project is wasted when wading through AI generated content.