Bug? Just got an email warning me about abuse-detection systems.

[AceVentura]

Select Topic Area

Bug

Body

On behalf of the GitHub Security team, I want to first extend our gratitude for your continued use of GitHub and for being a valued member of the >GitHub community.

Recent activity on your account caught the attention of our abuse-detection systems. This activity included use of Copilot that was indicative of >scripted interactions or of an otherwise deliberately unusual or strenuous nature. While we have not yet restricted Copilot access for your account, >further anomalous activity could result in a temporary suspension of your Copilot access.

While I’m unable to share specifics on rate limits, we prohibit all use of our servers for any form of excessive automated bulk activity, as well as any >activity that places undue burden on our servers through automated means. Please refer to our Acceptable Use Policies on this topic: >https://docs.github.com/site-policy/acceptable-use-policies/github-acceptable-use-policies#4-spam-and-inauthentic-activity-on-github.

Please also refer to our Terms for Additional Products and Features for GitHub Copilot for specific terms: https://docs.github.com/site-policy/github->terms/github-terms-for-additional-products-and-features#github-copilot.

Sincerely,
GitHub Security

I have no idea why I'm receiving this. I'm barely using copilot (mostly to generate ai messages for commits).
I don't have any other sessions, and I have checked the security logs, nothing wrong with them, so it can't be someone else using my account.

This sounds like a bug, anyone else is getting this?

[cristi-envato]

Same for me, I received the message about an hour ago.

[x-typo]

Same.pretty sure I didn't spam the requests to trigger this kind of behavior...

[dse82]

Same here, also just two hours ago. I even received the same email again twenty minutes later. Also not using copilot much (at least actively to my knowledge. don’t know what vscodes integration might do by itself …).

Must be a bug in the abuse detection or in microsoft’s very own copilot-integration plugin.

[marty0678]

Just got the same thing and thought it was spam. I'm contacting support to verify as the email is a bit sus to confirm if this is legit. Can't imagine how I did this, but I wonder if it's a bug in VsCode somewhere.

I remember at one point I was rate limited from GitHub for a while because their Pull Request VsCode extension was spamming their API, triggering rate limits, and locked me out of my account. That went on for a week until they fixed it, so wonder if it's a similar thing here that we aren't aware of.

[jeremydavidson]

Same... using it during normal coding day, but nothing scripted, bulk, or excessive at least not intentionally. I wonder if we'll soon get a follow up like "sorry, this email went out to more users than intended".

[vstyler96]

Same, I received this email an hour ago! It was a regular day usage, or even less

[sgoedecke]

Hi folks, I work on abuse for GitHub. I can confirm that this was an error on our end, as many of you anticipated: we sent out warnings to a group of users that shouldn't have been warned. We've fixed the core problem - no more warnings are going out - and we've scrubbed the warnings from our system. Sorry about that!

[DavidZidar]

Hi, please email affected users about what happened and confirm that they did nothing wrong. I only found this thread because I was about to file a support request about this issue.

[marty0678]

Support responded to me saying it was a legit warning and they can't comment on specifics but seemed to imply I was doing something I shouldn't. I asked for clarity and linked this response. I am assuming support just hasn't been updated on this issue but will update when I hear back.

[anhduc130]

+1 to @DavidZidar , please send out another email to that "shouldn't have been warned group of users", confirming that they're not the target. Thanks!

[ellisio]

I have been noticing Github > Copilot > Editor: Enable Code Actions, if enabled, has been causing some extreme delay on save over the last couple days. If I turn this off, the delay stops and files save normally.

At first, I thought it was ESLint's extension slowing down (happens from time to time). But, receiving this email made me go digging because I don't use Copilot outside of day-to-day activities working on code.

Perhaps this is related to the "abuse"? Maybe a bug in the extension causing several API calls/retries?