Reviewing requests to bypass push protection

You can use security overview to review requests to bypass push protection from contributors pushing to repositories across your organization.

¿Quién puede utilizar esta característica?

El acceso requiere:

  • Vistas de la organización: acceso de escritura a repositorios de la organización
  • Vistas de la empresa: propietarios de la organización y administradores de seguridad

Organizaciones que pertenecen a una cuenta de GitHub Team con GitHub Secret Protection, o propiedad de una cuenta GitHub Enterprise

En este artículo

About bypass requests

If your organization has configured delegated bypass for push protection, a designated team of reviewers controls which organization members can push secrets to repositories in your organization, and which members must first make a "bypass request" in order to push the secret.

On the "Push protection bypass" page in security overview, reviewers can find, review (approve or deny) and manage these requests.

For more information, see Managing requests to bypass push protection.

Reviewing bypass requests for an organization

  1. En GitHub, navega a la página principal de tu organización.

  2. Debajo del nombre de la organización, haz clic en Security.

    Captura de pantalla de la barra de navegación horizontal de una organización. Una pestaña, etiquetada con un icono de escudo y "Seguridad", está resaltado en naranja oscuro.

  3. In the sidebar, under "Requests", click Push protection bypass.

  4. Select the All statuses dropdown menu, then click Open to view requests that are awaiting review, or that have been approved but for which the commits haven't been pushed to the repository yet.

  5. Click the request that you want to review.

  6. Review the details of the request.

  7. Opcionalmente, agrega un comentario de revisión. El comentario se agregará a la escala de tiempo de la solicitud de revisión y la escala de tiempo de alerta de secret scanning. Por ejemplo, puede que quieras explicar el motivo de la aprobación o denegación de la solicitud de auditoría y de informes, y sugerir los pasos siguientes que tenga que seguir el colaborador.

  8. To allow the contributor to push the commit containing the secret, click Approve bypass request. Or, to require the contributor to remove the secret from the commit, click Deny bypass request.

Filtering requests

You can filter requests by repository, approver (member who has reviewed the request), requester (contributor making the request), timeframe, and status.

Filtering by status

The following statuses are assigned to a request:

StatusDescription
ApprovedThe request has been approved, but the commit(s) have not yet been pushed to the repository.
CancelledThe request has been cancelled by the contributor.
CompletedThe request has been approved and the commit(s) have been pushed to the repository, or the request was rejected.
DeniedThe request has been reviewed and denied.
ExpiredThe request has expired. Requests are valid for 7 days.
OpenThe request has not yet been reviewed.

Further reading