jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-19 18:10:59 -05:00
Code Issues Projects Releases Wiki Activity

Clarify approval requirement in delegated bypass documentation (#58564)

Browse Source 
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: MakeItSoKrystal <82061626+MakeItSoKrystal@users.noreply.github.com>
Co-authored-by: mc <42146119+mchammer01@users.noreply.github.com>
This commit is contained in:
Copilot
2025-11-21 09:22:54 +00:00
committed by GitHub
parent 6fb6245011
commit dd72c3bca6
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
content/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/about-delegated-bypass-for-push-protection.md
View File

@@ -19,7 +19,7 @@ shortTitle: About delegated bypass
{% data reusables.secret-scanning.push-protection-delegate-bypass-beta-note %} {% data reusables.secret-scanning.push-protection-delegate-bypass-beta-note %}
By default, when push protection is enabled for a repository, anyone with write access can still push a secret to the repository, provided that they specify a reason for bypassing push protection. When push protection is enabled for a repository, users with write access can bypass push protection and push a secret if they provide a reason and the bypass is approved.
With delegated bypass for push protection, you can: With delegated bypass for push protection, you can: