Secret scanning detects secrets in GitHub Actions workflow logs
GitHub secret scanning now scans GitHub Actions workflow logs for provider secret patterns after a run completes, in addition to issues, wikis, discussions, and pull requests. Findings appear in the repository's secret scanning alert list with a link back to the workflow log, and validity checks run for supported secret types. The feature is in public preview for GitHub Enterprise Cloud customers with GitHub Secret Protection or GitHub Advanced Security, and is disabled by default.
What changes for platform teams
Platform teams on GitHub Actions can enable an enterprise-wide policy to catch leaked credentials in workflow logs, but only runs completed after enabling are scanned and generic, custom, and AI-detected secrets are not. Alerts do not send notifications during the preview, so teams must check the alert list directly.
Read the original at GitHub Changelog ↗
written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules