Note
Delegated bypass for push protection is currently in beta and subject to change.
Delegated bypass for push protection lets you define who can push commits containing secrets and adds an approval process for other contributors. See About delegated bypass for push protection.
To enable delegated bypass, create the teams or roles that will manage bypass requests.
Enabling delegated bypass for a repository
Note
If an organization or enterprise owner configures delegated bypass at the organization or enterprise level, the repository-level settings are disabled.
-
On GitHub, navigate to the main page of the repository.
-
Under your repository name, click Settings. If you cannot see the "Settings" tab, select the dropdown menu, then click Settings.
-
In the "Security" section of the sidebar, click Code security and analysis.
-
Under "Code security and analysis", find "GitHub Advanced Security."
-
Under "Push protection," to the right of "Who can bypass push protection for secret scanning," select the dropdown menu, then click Specific roles or teams.
-
Under "Bypass list," click Add role or team.
-
In the dialog box, select the roles and teams that you want to add to the bypass list, then click Add selected.
Note
You can't add secret teams to the bypass list.
Enabling delegated bypass for an organization
-
On GitHub, navigate to the main page of the organization.
-
Under your organization name, click Settings. If you cannot see the "Settings" tab, select the dropdown menu, then click Settings.
-
In the "Security" section of the sidebar, click Code security and analysis.
-
Under "Code security and analysis", find "GitHub Advanced Security."
-
Under "Push protection," to the right of "Who can bypass push protection for secret scanning," select the dropdown menu, then click Specific roles or teams.
-
Under "Bypass list," click Add role or team.
-
In the dialog box, select the roles and teams that you want to add to the bypass list, then click Add selected.