# Managing requests to bypass push protection
As a member of the bypass list for an organization or repository, you can review bypass requests from other members of the organization or repository.
When delegated bypass for push protection is enabled, designated reviewers can approve or deny requests from contributors who want to push commits containing secrets.
This article explains how to review and manage bypass requests for repositories and organizations.
For more information about how bypass requests work, see [Demandes de contournement pour la protection de l’envoi](/fr/code-security/concepts/secret-security/about-bypass-requests-for-push-protection).
## Managing requests for a repository
1. Sur GitHub, accédez à la page principale du référentiel.
2. Sous le nom du référentiel, cliquez sur l’onglet ** Security and quality** . Si vous ne voyez pas l’onglet « Security and quality », sélectionnez le **** menu déroulant, puis cliquez sur ** Security and quality**.
3. Dans la barre latérale gauche, sous « Demandes », cliquez sur **Ignorer la protection Push**.
4. Select the **All statuses** dropdown menu, then click **Open** to view requests that are awaiting review, and those 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. Si vous le souhaitez, vous pouvez ajouter un commentaire de révision. Le commentaire sera ajouté à la chronologie des demandes de révision et à la chronologie des alertes secret scanning. Par exemple, vous pouvez expliquer la raison de l’approbation ou du refus de la demande pour des raisons d’audit et de création de rapports, et suggérer les prochaines étapes que doit suivre le contributeur.
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**.
## Managing requests for an organization
Organization owners, security managers and organization members with the relevant fine-grained permission (via a custom role) can review and manage bypass requests for all repositories in the organization using security overview. See [Examen des demandes de contournement de la protection par push](/fr/code-security/security-overview/reviewing-requests-to-bypass-push-protection).
## Filtering requests
You can filter requests by:
* Approver (member of the bypass list)
* Requester (contributor making the request)
* Timeframe
* Status
### Filtering by status
The following statuses are assigned to a request:
| Status | Description |
| ----------- | ---------------------------------------------------------------------------------------------------------------------------- |
| `Cancelled` | The request has been canceled by the contributor. |
| `Completed` | The request has been approved and the commit(s) have been pushed to the repository. |
| `Denied` | The request has been reviewed and denied. |
| `Expired` | The request has expired. Requests are valid for 7 days. |
| `Open` | The request has either not yet been reviewed, or has been approved but the commit(s) have not been pushed to the repository. |
## Further reading
* [Contournement délégué pour la protection contre les poussées](/fr/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/about-delegated-bypass-for-push-protection)
* [Enabling delegated bypass for push protection](/fr/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/enabling-delegated-bypass-for-push-protection)
* [Examen des demandes de contournement de la protection par push](/fr/code-security/security-overview/reviewing-requests-to-bypass-push-protection)