GitHub narrows when weekly code scans begin

GitHub has changed when weekly scheduled scans begin for code scanning default setup and GitHub Code Quality: a push or pull request must first trigger an analysis. The prior activity measure counted any unscheduled scan, including initial validation runs and scans prompted by newly detected languages. Enabling default setup still runs a validation scan and populates findings right away, but that scan alone does not start weekly scanning. The activity check uses analysis history rather than Git activity from before scanning was enabled, and activity remains shared between code scanning and Code Quality. The change is available on GitHub Enterprise Cloud and will be supported in GitHub Enterprise Server 3.24. Administrators managing these tools across many repositories should see fewer unexpected weekly scans on repositories without recent development activity; no configuration change is needed.