Anyone else get a vague GitHub shakedown notice?

jjgreen 48 points 43 comments July 10, 2026
lists.osgeo.org · View on Hacker News

Discussion Highlights (11 comments)

jjgreen

A QGIS-Developer post, original title anyone else get a vague github shakedown notice? is this about qgis?

OptionOfT

I got the same email, and I don't have a credit card on file with them. I wonder what they're going to do?

dewey

What about this email is a "shakedown"?

pocksuppet

No, I didn't, because I quit GitHub when they started demanding mandatory SMS 2FA

andai

This links to this, which says https://docs.github.com/en/code-security/concepts/about-code... > GitHub Code Quality is currently in public preview and will become generally available on July 20, 2026. During public preview, Code Quality scans will consume GitHub Actions minutes but you will not be billed for other usage. From July 20, 2026, usage will incur additional charges. See GitHub Code Quality billing. >If you want to avoid charges, disable Code Quality before July 20, 2026. See Disabling GitHub Code Quality. https://docs.github.com/en/code-security/how-tos/maintain-qu... >( Repo > Settings > Code Quality) I don't see that tab, so either the docs are out of date, and it's called something else now, or it's not on all accounts/all repos. (Due to being in preview?) I don't know.

dumbfoundded

It sounds like they gave you a feature for free you didn't want, and now are trying to charge for it. Very much a dark pattern.

Aurornis

I'm a GitHub admin. Did not receive this e-mail. We don't have the GitHub Code Quality feature enabled anywhere, though. The e-mail seems clear: Someone enabled the feature in the organization. The feature was in free preview, but the free preview is ending. If they leave it enabled, it will be billed at the new rate. It's pretty clear that "organization" is being used throughout the e-mail, so they're not referring to this person's free personal GitHub account.

hkchad

Uh? What? Shakedown? You enabled a free preview of a paid service, they are now letting you know what it will cost to continue to use a paid for service, how on earth is this a 'shake down'? GitHub deserves a lot of crap, but not for this.

cush

> More details are available in our documentation ( https://docs.github.com/code-security/concepts/about-code-qu... ). ^^^

rurban

This is about an optional setting for org admins you need to disable in the repo settings, Security and Quality. Not vague at all.

carogalvin

Hi, I'm the PM who sent out this email! This email only went out to enterprise admins where there's an org somewhere that has Code Quality enabled on some repository. It's very possible that, due to what you mentioned about adjusting roles and organization membership recently, that it no longer applies to you and we didn't update our filter in time. To be super sure that you turn it off everywhere if you don't want to pay for it, go to any organizations you're the admin for, and go to Settings > Code Quality (it'll be in the left side bar), say "No repos" for the "Repo Access" dropdown, and turn on enforcement - it'll then turn it off everywhere in the org and stop it from being turned back on (in very large orgs, this can take a few minutes to propagate).

Semantic search powered by Rivestack pgvector
14,015 stories · 131,331 chunks indexed