Yes an additional interaction via mailing list, where the PR is explained helps us to at least make the probability higher for an actual person and not a bot generating code.
Am 7. Oktober 2025 14:23:13 MESZ schrieb Christofer Dutz <[email protected]>: >Hi all, > >Afer we jus got another set of AI PRs, I think we should discuss how to >generally handle these types of PRs. > >They usually handle super trivial stuff where merging is sort of a no-brainer. >However, merging a PR gives access to some GitHub Runner resources. It also >lets „AI contributors“ appear more credible in other projects (if you don’t >actually look at the PRs that got merged). > >I personally would like us to live the Apache moto: "Community over Code“. > >What do you think? Should we make communicating on the mailing list before >having PRs merged mandatory? If the submitter declines or disappears, we >simply replicate the changes and close that door for automated PRs. > >What do you think? I would like to add this requirement. Email … slack … up to >them … I just want some form of interaction that helps us at least raise the >bar for AI bots. > >Chris >
