This version of GitHub Enterprise Server was discontinued on 2024-09-25. No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, upgrade to the latest version of GitHub Enterprise Server. For help with the upgrade, contact GitHub Enterprise support.

My commit is blocked by push protection

To keep your repository secure, push protection prevents you from accidentally committing secrets to the repository.

In this article

Understanding why push protection has blocked your commit

Leaked secrets can pose serious security risks to your repository and your supply chain. Push protection prevents you from accidentally introducing secrets to your codebase where they could be exploited by malicious actors.

If the repository you're contributing to on GitHub is secured by push protection, you'll encounter a push protection block whenever you:

  • Push commits containing recognized secrets from the command line to the remote repository.
  • Commit changes containing recognized secrets to a repository in the GitHub UI.

Resolving a push protection block

In order to resolve the block, you should remove the secret from the commit . If you believe the secret is safe to push, you may be able to bypass the block. For more information on how to remove the secret or, if necessary, bypass the block, see:

Further reading