Merge pull request github#34938 from github/repo-sync

Repo sync

content/code-security/secret-scanning/introduction/about-push-protection.md

@@ -41,7 +41,8 @@ For information about the secrets and service providers supported by push protec
 Push protection works:
 
 * From the command line. See "[AUTOTITLE](/code-security/secret-scanning/working-with-secret-scanning-and-push-protection/working-with-push-protection-from-the-command-line)."
-* In the {% data variables.product.prodname_dotcom %} UI. See "[AUTOTITLE](/code-security/secret-scanning/working-with-secret-scanning-and-push-protection/working-with-push-protection-in-the-github-ui)."{% ifversion secret-scanning-push-protection-content-endpoints %}
+* In the {% data variables.product.prodname_dotcom %} UI. See "[AUTOTITLE](/code-security/secret-scanning/working-with-secret-scanning-and-push-protection/working-with-push-protection-in-the-github-ui)."{% ifversion push-protection-delegated-bypass-file-upload-support %}
+* On files uploaded onto the repository on {% data variables.product.prodname_dotcom %}.{% endif %}{% ifversion secret-scanning-push-protection-content-endpoints %}
 * From the REST API. See "[AUTOTITLE](/code-security/secret-scanning/working-with-secret-scanning-and-push-protection/working-with-push-protection-from-the-rest-api)."{% endif %}
 
 Once enabled, if push protection detects a potential secret during a push attempt, it will block the push and provide a detailed message explaining the reason for the block. You will need to review the code in question, remove any sensitive information, and reattempt the push.

content/code-security/secret-scanning/working-with-secret-scanning-and-push-protection/working-with-push-protection-in-the-github-ui.md

@@ -17,7 +17,7 @@ topics:
 
 ## About push protection in the {% data variables.product.prodname_dotcom %} UI
 
-When you are creating and editing files in the {% data variables.product.prodname_dotcom %} UI, push protection prevents you from accidentally committing secrets to a repository by blocking commits containing supported secrets.
+When you {% ifversion push-protection-delegated-bypass-file-upload-support %}upload, create, {% else %}create {% endif %}or edit files from the {% data variables.product.prodname_dotcom %} UI, push protection prevents you from accidentally committing secrets to a repository by blocking commits containing supported secrets.
 
 {% ifversion push-protection-block-uploads %}
 

data/features/push-protection-delegated-bypass-file-upload-support.yml

@@ -0,0 +1,4 @@
+# Issue 16148 - Push protection delegated bypass for file uploads [GA]
+versions:
+  ghec: '*'
+  ghes: '>3.15'

data/reusables/secret-scanning/push-protection-delegated-bypass-intro.md

@@ -1 +1 @@
-Delegated bypass for push protection lets you define contributors who can bypass push protection and adds an approval process for other contributors.
+Delegated bypass for push protection lets you define contributors who can bypass push protection and adds an approval process for other contributors.{% ifversion push-protection-delegated-bypass-file-upload-support %} Delegated bypass applies to files created, edited, and uploaded on {% data variables.product.prodname_dotcom %}.{% endif %}