This feature proactively prevents leaks by scanning for secrets before 'git push' operations are accepted, and it works with 69 token types (API keys, private keys, secret keys, authentication ...

Because a token leak is a security vulnerability, the naive solution that often comes to mind is to remove the key from the code and publish a new, “fixed” version, same as with a CVE.