{"meta":{"title":"Managing requests to bypass push protection","intro":"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.","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/manage-bypass-requests","title":"Manage bypass requests"},{"href":"/en/code-security/how-tos/secure-your-secrets/manage-bypass-requests/manage-bypass-requests","title":"Manage bypass requests"}],"documentType":"article"},"body":"# Managing requests to bypass push protection\n\nAs a member of the bypass list for an organization or repository, you can review bypass requests from other members of the organization or repository.\n\nWhen delegated bypass for push protection is enabled, designated reviewers can approve or deny requests from contributors who want to push commits containing secrets.\n\nThis article explains how to review and manage bypass requests for repositories and organizations.\n\nFor more information about how bypass requests work, see [Bypass requests for push protection](/en/code-security/concepts/secret-security/about-bypass-requests-for-push-protection).\n\n## Managing requests for a repository\n\n1. On GitHub, navigate to the main page of the repository.\n\n2. Under the repository name, click the ** Security and quality** tab. If you cannot see the \" Security and quality\" tab, select the **** dropdown menu, and then click ** Security and quality**.\n\n3. In the left sidebar, under \"Requests,\" click **Push protection bypass**.\n\n4. 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.\n\n5. Click the request that you want to review.\n\n6. Review the details of the request.\n\n7. Optionally, add a review comment. The comment will be added to the review request timeline and the secret scanning alert timeline. For example, you may wish to explain the reason for the approval or denial of the request for auditing and reporting reasons, and suggest next steps for the contributor to take.\n\n8. 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**.\n\n## Managing requests for an organization\n\nOrganization 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 [Reviewing requests to bypass push protection](/en/code-security/security-overview/reviewing-requests-to-bypass-push-protection).\n\n## Filtering requests\n\nYou can filter requests by:\n\n* Approver (member of the bypass list)\n* Requester (contributor making the request)\n* Timeframe\n* Status\n\n### Filtering by status\n\nThe following statuses are assigned to a request:\n\n| Status | Description |\n| ----------- | ---------------------------------------------------------------------------------------------------------------------------- |\n| `Cancelled` | The request has been canceled by the contributor. |\n| `Completed` | The request has been approved and the commit(s) have been pushed to the repository. |\n| `Denied` | The request has been reviewed and denied. |\n| `Expired` | The request has expired. Requests are valid for 7 days. |\n| `Open` | The request has either not yet been reviewed, or has been approved but the commit(s) have not been pushed to the repository. |\n\n## Further reading\n\n* [Delegated bypass for push protection](/en/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/about-delegated-bypass-for-push-protection)\n* [Enabling delegated bypass for push protection](/en/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/enabling-delegated-bypass-for-push-protection)\n* [Reviewing requests to bypass push protection](/en/code-security/security-overview/reviewing-requests-to-bypass-push-protection)"}