✔️ Linting Passed

All linting checks passed. Your pull request is in excellent shape! ☀️

_{Generated for commit:b2af442. Link to the linter CI:here}

Here is some evidence of the problem.

Examples:
#31581
#31649
#31597
#31602
#31684

Extend:
You can see that there is an increasing amount of partially or fully generated PRs and a decrease in overall quality for PRs by looking atthe last closed PRs. Quite some of the authors also spam-open llm-based PRs on other open source projects at the same time.

@StefanieSenger Once this wording is refined, the Contributing Guide is another place where it could be added.

Do you know what tools people are/could be using for this? If we do find out then we could test drive the template to see if it does anything.

Could we move it to the end of the template? That way the message for robots wouldn't take up valuable space at the top. It feels wrong/annoying to optimise for the abusers instead of the good people (who all have to wade through the message till they get to the stuff they should read).

Do you know what tools people are/could be using for this? If we do find out then we could test drive the template to see if it does anything.

The cause seems to be that GitHub has recently allowed AI generated issues and PRs (and even sells it) via Copilot.
See this community discussion:Allow us to block Copilot-generated issues (and PRs) from our own repositories.

Github even promotes this on its blog:How to create issues and pull requests in record time on GitHub.

I have just added this information in the PR description.

(Though it seems there were ways to generate PRs for a while. I found some "older" instrucions like this medium article from december 2023:Let AI generate Pull Requests from your GitHub issues!.)

Oh this is an interesting idea. Could you maybe test it on your fork, and see what happens with this when you try to open a PR with copilot to your fork?

Investigating this, it seems the copilot button on the repo doesn't work, since we haven't setup codespaces. Which means LLM generated PRs are created manually in a user's IDE? That would mean this would have no effect unless the LLM ends up reading this file. By the time the user creates a PR, it's too late and usually the work for the PR is already done.