GitHub secret scanning now checks GitHub Actions workflow logs in public preview, and alerts survive log deletion
Secrets leaked into CI logs will finally get caught. What it scans, what it misses and who can turn it on.
// Key points
- When a workflow run completes, GitHub scans its logs for provider patterns; findings land in the repository's secret scanning alert list with a link back to the log, and validity checks run for supported types.
- It is for GitHub Enterprise Cloud enterprises with GitHub Secret Protection or Advanced Security; the policy is off by default and enterprise owners enable it under Policies, then Advanced Security.
- Only runs completed after enabling are scanned, with no backfill; generic patterns, custom patterns, AI-detected secrets and secrets already masked by Actions are not detected, and alerts send no notifications during the preview.
Builder's takeAgents increasingly run commands and print environments inside CI, and logs are where secrets leak most easily. If you qualify, turn it on now, and since the preview sends no notifications, have someone check the alert list on a schedule; if you do not, at least audit which jobs echo env into their logs.
// Background · from #Coding agents
Full timeline →- Nov 10 Anthropic releases Claude Fable 5.2 and Mythos 5.2 at $8 input and $40 output per million tokens, scoring 49.1% on FrontierCode 2.0
- Nov 9 Google measures agent distraction: 13% of sessions meet bug-referencing TODOs, and detoured sessions take 70% more steps and 77% more tokens
- Nov 9 The Copilot app sets up Agent Merge from a pull request and adds assisted approval: tell Copilot in your own words which tool requests to approve automatically