This version of GitHub Enterprise Server will be discontinued on 2025-08-27. 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.
Delegated bypass for push protection
You can control the ability to bypass push protection by setting up a reviewers group to assess requests. When a contributor proposes bypassing protections, any member of the bypass list can approve or block the request.
Who can use this feature?
Secret scanning is available for the following repository types:
- Organization-owned repositories with GitHub Advanced Security enabled
- User-owned repositories for enterprises with GitHub Advanced Security enabled
About delegated bypass for push protection
You can control which teams or roles have the ability to bypass push protection in your organization or repository.
Enabling delegated bypass for push protection
You can use delegated bypass for your organization or repository to control who can push commits that contain secrets identified by secret scanning.
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.