Hello! I am an engineer on the Secret Scanning team, thanks for the kind words! - "push protection" (as we call it) isn't available for free, and isn't part of

Hello! I am an engineer on the Secret Scanning team, thanks for the kind words! - "push protection" (as we call it) isn't available for free, and isn't part of this rollout. - For folks who do pay, the flow may be: a developer tries to push, they bypass the secret, are now able to push. From there, an alert is created which they can resolve (maybe it is "used in tests"). - If the _same_ secret is pushed again, we won't block that push. We also won't create a new alert; however, a new location may be recorded within the resolved alert (if you click into it). If you're seeing push _not_ get blocked, what's most likely is that we just don't support that specific token as part of push protection (we have some much-needed improvements to do to the docs to make this more clear). Since push protection sits in front of the developer, we try not to annoy them with high-false positive tokens. There are a few other possibilities though, so hard to say.