Esta versão do GitHub Enterprise Server foi descontinuada em 2026-03-17. Nenhum lançamento de patch será feito, mesmo para questões críticas de segurança. Para obter melhor desempenho, segurança aprimorada e novos recursos, atualize para a última versão do GitHub Enterprise Server. Para obter ajuda com a atualização, entre em contato com o suporte do GitHub Enterprise.

Habilitar o bypass delegado para proteção de push

Controlar quem pode enviar por push o código que contém segredos exigindo aprovação de bypass de revisores designados.

Quem pode usar esse recurso?

Proprietários de repositórios, proprietários de organizações, gerentes de segurança e usuários com a função de administrador

Neste artigo

Observação

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

Observação

If an organization owner configures delegated bypass at the organization-level, the repository-level settings are disabled.

  1. On GitHub, navigate to the main page of the repository.

  2. Under your repository name, click Settings. If you cannot see the "Settings" tab, select the dropdown menu, then click Settings.

    Screenshot of a repository header showing the tabs. The "Settings" tab is highlighted by a dark orange outline.

  3. In the "Security" section of the sidebar, click Code security and analysis.

  1. Under "Code security and analysis", find "GitHub Advanced Security."

  2. 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.

  3. Under "Bypass list," click Add role or team.

    Observação

    When you add roles or teams to the "bypass list," these users will be granted the ability to bypass push protection, and they can also review and manage the requests from all other contributors to bypass push protection.

    You can't add secret teams to the bypass list.

  4. In the dialog box, select the roles and teams that you want to add to the bypass list, then click Add selected.

Enabling delegated bypass for an organization

  1. On GitHub, navigate to the main page of the organization.

  2. Under your organization name, click Settings. If you cannot see the "Settings" tab, select the dropdown menu, then click Settings.

    Screenshot of the tabs in an organization's profile. The "Settings" tab is outlined in dark orange.

  3. In the "Security" section of the sidebar, click Code security and analysis.

  1. Under "Code security and analysis", find "GitHub Advanced Security."

  2. 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.

  3. Under "Bypass list," click Add role or team.

  4. In the dialog box, select the roles and teams that you want to add to the bypass list, then click Add selected.