{"meta":{"title":"How-tos for leak prevention","intro":"Learn how to prevent future secret leaks with GitHub's push protection.","product":"Security and code quality","breadcrumbs":[{"href":"/en/code-security","title":"Security and code quality"},{"href":"/en/code-security/how-tos","title":"How-tos"},{"href":"/en/code-security/how-tos/secure-your-secrets","title":"Secure your secrets"},{"href":"/en/code-security/how-tos/secure-your-secrets/prevent-future-leaks","title":"Prevent future leaks"}],"documentType":"subcategory"},"body":"# How-tos for leak prevention\n\nLearn how to prevent future secret leaks with GitHub's push protection.\n\n## Links\n\n* [Enabling push protection for your repository](/en/code-security/how-tos/secure-your-secrets/prevent-future-leaks/enabling-push-protection-for-your-repository)\n\n  With push protection, secret scanning blocks contributors from pushing secrets to a repository and generates an alert whenever a contributor bypasses the block.\n\n* [Managing push protection for users](/en/code-security/how-tos/secure-your-secrets/prevent-future-leaks/manage-user-push-protection)\n\n  You can control GitHub's ability to block your pushes that may contain secrets."}