GitHub Copilot Agent - a new thread to maintainers?

Just the day GitHub released Copilot Agents to the public, I had to remove spam issues and PRs from the PHP track. I handed the spam to GitHub support and they removed everything completely within a day.

Of course, it might not have been AI generated stuff. But it connected both things in my mind. Has anybody had to fight spam in their GitHub repositories, yet? Was it unlucky me?

The Python track has been getting 1-2 spam issues/PRs every few days for the last month - six weeks, or maybe even longer (it took me a while to notice it with the auto closer action on).

They’re all from accounts that are newly created, who then have the spam as their only activity. Sometimes, the accounts and spam are created on the same day, and sometimes there is a 2-3 day delay between account creation and the spam.

Github is usually really good about investigating and then removing things/suspending accounts. However, one day I had 4 of these crop up, and they wouldn’t let me report the last two because it triggered their spam rules! :rofl:

I’ve also seen some spam posts on the d track, so I am assuming that this is an issue across many tracks, but maybe not easily noticed due to our auto-close actions, and general maintainer load and activities.

1 Like

There has also been GitHub spam on the Lua track.

1 Like

OK, so it is not a new / unique thing but also not too common and often. It’s not prevented by auto-closing, so I have no other option but report when it happens. And hope that some billion of repositories are enough of choice so it does not hit me too often. Thanks!

(Edit: There’s no way to have 2 solutions, so chose my conclusion)

1 Like