Push protection is enabled for free users on GitHub #110557
Unanswered
courtneycl
asked this question in
Code Security
Replies: 1 comment 2 replies
-
This is great news. and I believe it's a big leap to have push protection enabled by default. My question is: what about private repositories which will change to public, will those get scanned before going public by default as well? |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
👋 Hello from the secret scanning team!
We have some news: we've started the rollout for enabling push protection on all free user accounts on GitHub. This automatically protects you from accidentally committing secrets to public repositories, regardless of whether the repository itself has secret scanning enabled.
If a secret is detected in any push to a public repository, your push will be blocked. You will have the option to remove the secret from your commits or, if you deem the secret safe, bypass the block.
It might take a week or two for this change to apply to your account; you can verify status and opt-in early in your code security and analysis settings. Once enabled, you also have the option to opt-out. Disabling push protection may cause secrets to be accidentally leaked.
Any feedback? Let us know 👇 ❤️
Beta Was this translation helpful? Give feedback.
All reactions