Skip to main content

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 organization-owned repositories, and in beta for user-owned repositories in GitHub Enterprise Server if your enterprise has a license for GitHub Advanced Security. For more information, see "About secret scanning alerts" and "About GitHub Advanced Security."

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.