2694dd5fe4
Co-authored-by: mc <42146119+mchammer01@users.noreply.github.com> Co-authored-by: github-actions <github-actions@github.com> Co-authored-by: Joe Clark <31087804+jc-clark@users.noreply.github.com>
1.9 KiB
title, intro, versions, type, topics
| title | intro | versions | type | topics | ||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Push protection for users | You can use {% data variables.product.prodname_secret_scanning %} to block commits containing secrets in any public repository by enabling push protection for yourself. |
|
how_to |
|
{% data reusables.secret-scanning.push-protection-for-users-beta %}
About push protection for users
With push protection for users, you can enable push protection for yourself, so that no matter which public repository you push to, you will be protected. Additionally, if you are a repository administrator, or an organization owner, you can enable push protection for your repository or organization, respectively. For more information, see "AUTOTITLE."
If push protection is not enabled for the repository you are pushing to, but you have push protection for yourself enabled, no alerts will be created after you push a secret. However, if the bypassed secret is a {% data variables.product.prodname_dotcom %} token, the token will be revoked and you will be notified by email.
For information on the secrets and service providers supported for push protection, see "AUTOTITLE."
Enabling push protection for yourself
You can enable push protection for yourself through your personal account settings.
{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.security-analysis %}
-
Under "User", to the right of "Push protection for yourself", click Enable.
