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

Fast follow: Reviewers can add a comment on push protection bypass requests for secret scanning [GA] (#53525)

Browse Source 
Co-authored-by: Siara <108543037+SiaraMist@users.noreply.github.com>
This commit is contained in:
Vanessa
2024-12-10 08:52:02 +10:00
committed by GitHub
parent 9e41eaeabc
commit fda940b05e
4 changed files with 12 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
content/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/delegated-bypass-for-push-protection/managing-requests-to-bypass-push-protection.md
View File

@@ -46,6 +46,9 @@ The contributor is notified of the decision by email and must take the required
1. Select the **All statuses** dropdown menu, then click **Open** to view requests that are awaiting review, and those that have been approved but for which the commits haven't been pushed to the repository yet. 1. Select the **All statuses** dropdown menu, then click **Open** to view requests that are awaiting review, and those that have been approved but for which the commits haven't been pushed to the repository yet.
1. Click the request that you want to review. 1. Click the request that you want to review.
1. Review the details of the request. 1. Review the details of the request.
{% ifversion push-protection-bypass-reviewer-comment -%}
{% data reusables.repositories.bypass-requests-reviewer-comment %}
{%- endif %}
1. To allow the contributor to push the commit containing the secret, click **Approve bypass request**. Or, to require the contributor to remove the secret from the commit, click **Deny bypass request**. 1. To allow the contributor to push the commit containing the secret, click **Approve bypass request**. Or, to require the contributor to remove the secret from the commit, click **Deny bypass request**.
{% ifversion security-overview-delegated-bypass-requests %} {% ifversion security-overview-delegated-bypass-requests %}

3
content/code-security/security-overview/reviewing-requests-to-bypass-push-protection.md
View File

@@ -31,6 +31,9 @@ For more information, see "[AUTOTITLE](/code-security/secret-scanning/using-adva
1. Select the **All statuses** dropdown menu, then click **Open** to view requests that are awaiting review, or that have been approved but for which the commits haven't been pushed to the repository yet. 1. Select the **All statuses** dropdown menu, then click **Open** to view requests that are awaiting review, or that have been approved but for which the commits haven't been pushed to the repository yet.
1. Click the request that you want to review. 1. Click the request that you want to review.
1. Review the details of the request. 1. Review the details of the request.
{% ifversion push-protection-bypass-reviewer-comment -%}
{% data reusables.repositories.bypass-requests-reviewer-comment %}
{%- endif %}
1. To allow the contributor to push the commit containing the secret, click **Approve bypass request**. Or, to require the contributor to remove the secret from the commit, click **Deny bypass request**. 1. To allow the contributor to push the commit containing the secret, click **Approve bypass request**. Or, to require the contributor to remove the secret from the commit, click **Deny bypass request**.
## Filtering requests ## Filtering requests

5
data/features/push-protection-bypass-reviewer-comment.yml Normal file
View File

@@ -0,0 +1,5 @@
# Reference: #16452
# Documentation for reviewers can add a comment on push protection bypass requests for secret scanning [GA]
versions:
ghec: '*'
ghes: '>3.16'

1
data/reusables/repositories/bypass-requests-reviewer-comment.md Normal file
View File

@@ -0,0 +1 @@
1. Optionally, add a review comment. The comment will be added to the review request timeline and the {% data variables.product.prodname_secret_scanning %} alert timeline. For example, you may wish to explain the reason for the approval or denial of the request for auditing and reporting reasons, and suggest next steps for the contributor to take.