(First posted on Gitter, suggested to raise on the ML for better exposure)
Cheers,
I am going through the paces with a newly hosted plugin, and comparing settings with others I maintain. As I was looking for the place to enable CodeQL checks to protect the main branch, I got to the page for enabling Code Quality, and for some reason it said it would be billed if enabled... never saw that one before. Any ideas why? Does GitHub not sponsor public FOSS projects anymore?

It may be possible that some of the repos I maintain had Code Quality enabled one way or another (including a mistake by me or predecessors), in Jenkins plugins and in other projects I deal with. I certainly do not remember authorizing any paid-for activity, so it is possible that these options were previously freely available and then GitHub changed its stance (if so - no idea whether for new enablements or revising the terms for existing ones too). Can someone please review what is the proper setup for these options, and if those already enabled repos are indeed paid-for and CQ should be disabled there to not suck $$$?
The page contents I see in e.g. NUT and in a different Jenkins hosted plugin are quite different (the latter has toggles for AI that could be billed)...
There are (also?) CodeQL settings under (well under, a few screens down) the Advanced Security page.
Notably, the freely accessible Advanced Security / (scroll down) / Code Security also has a toggle for AI that can suck credits (Copilot Autofix), but maybe that is less "scary" as GitHub does sponsor some amount of credits for FOSS maintainers, I don't know if/how that applies to Jenkins Org though:
TLDR FUD summary:
* maybe we have GitHub options enabled in the plugin ecosystem and other repos, which could suck money from the Jenkins Org budget,
* maybe they do or don't depending on when they were enabled and GH terms at that time,
* need to learn more, possibly go over all those repos to disable the options.
Hope this helps,
Jim Klimov