Skip to main content

Working with push protection from the REST API

Learn your options for unblocking your push to GitHub using the REST API if secret scanning detects a secret in the content of your API request.

¿Quién puede utilizar esta característica?

Usuarios con acceso de escritura

En este artículo

About push protection from the REST API

Push protection prevents you from accidentally committing secrets to a repository by blocking pushes containing supported secrets.

The "Create a blob" and "Create or update file contents" endpoints in the REST API include push protection. See Puntos de conexión de la API de REST para blobs de Git and Puntos de conexión de la API de REST para el contenido del repositorio.

If you make a request with these endpoints whose content includes a supported secret, the REST API will return a 409 error, indicating that a secret has been detected.

To resolve the error, you can either:

Further reading