Working with secret scanning and push protection
Secret scanning scans for and detects secrets that have been checked into a repository. Push protection proactively secures you against leaking secrets by blocking pushes containing secrets.
Who can use this feature?
Secret scanning alerts for partners runs automatically on public repositories and public npm packages to notify service providers about leaked secrets on GitHub.
Secret scanning alerts for users are available for user-owned public repositories for free. Organizations using GitHub Enterprise Cloud with a license for GitHub Advanced Security can also enable secret scanning alerts for users on their private and internal repositories. Additionally, secret scanning alerts for users are available and in beta on user-owned repositories for GitHub Enterprise Cloud with Enterprise Managed Users. For more information, see "About secret scanning alerts" and "About GitHub Advanced Security."
For information about how you can try GitHub Advanced Security for free, see "Setting up a trial of GitHub Advanced Security."
Push protection for users
With push protection for users, you are automatically protected on all pushes to public repositories across GitHub Enterprise Cloud.
Working with push protection from the command line
Learn your options for unblocking your push from the command line to GitHub if secret scanning detects a secret in your changes.
Working with push protection in the GitHub UI
Learn your options for unblocking your commit when secret scanning detects a secret in your changes.