Anyone else get a vague GitHub shakedown notice?
lists.osgeo.org
Anyone else get a vague GitHub shakedown notice?
1–10 of 51 posts
Re: Anyone else get a vague GitHub shakedown notice?
#2Re: Anyone else get a vague GitHub shakedown notice?
#3A QGIS-Developer post, original title anyone else get a vague github shakedown notice? is this about qgis?
Re: Anyone else get a vague GitHub shakedown notice?
#4Re: Anyone else get a vague GitHub shakedown notice?
#5Re: Anyone else get a vague GitHub shakedown notice?
#6What about this email is a "shakedown"?
Re: Anyone else get a vague GitHub shakedown notice?
#7What about this email is a "shakedown"?
Re: Anyone else get a vague GitHub shakedown notice?
#8Re: Anyone else get a vague GitHub shakedown notice?
#9https://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.
Re: Anyone else get a vague GitHub shakedown notice?
#10No, I didn't, because I quit GitHub when they started demanding mandatory SMS 2FA
As a matter of fact GH even has a red "Less secure" badge on the SMS 2FA in the settings discouraging its use, as well as the following text in the description: "We strongly advise against using SMS because it is susceptible to interception, does not provide resistance against phishing attacks, and deliverability can be unreliable."