Question

Your organization has enabled Push Protection with a delegated bypass policy. A developer without bypass privileges attempts to push a commit that contains a secret matching a supported pattern. According to the delegated bypass workflow, what happens next?

Accepted Answer

The push is blocked, and the developer must submit a bypass request that a designated reviewer in the bypass list must approve or deny before the push can proceed.

Answer

The push is silently accepted, but a secret scanning alert is generated for the security team to triage later.

Answer

The push is blocked permanently, and only an organization owner can remove the secret from the commit history on the developer's behalf.

Answer

The developer can immediately self-bypass by selecting a reason such as 'used in tests,' and the security team is notified afterward.