From 70cec296ced27b18589efb91b5b0a706a54c69a1 Mon Sep 17 00:00:00 2001 From: mc <42146119+mchammer01@users.noreply.github.com> Date: Wed, 11 Dec 2024 15:46:59 +0000 Subject: [PATCH 1/2] Note limitation for push protection in free public repositories (#53555) Co-authored-by: Courtney Claessens Co-authored-by: Vanessa --- .../secret-scanning/introduction/about-push-protection.md | 2 ++ .../troubleshooting-secret-scanning.md | 3 ++- 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/content/code-security/secret-scanning/introduction/about-push-protection.md b/content/code-security/secret-scanning/introduction/about-push-protection.md index 0c957edf3e26..dd50bc97f268 100644 --- a/content/code-security/secret-scanning/introduction/about-push-protection.md +++ b/content/code-security/secret-scanning/introduction/about-push-protection.md @@ -36,6 +36,8 @@ You can enable push protection: For information about the secrets and service providers supported by push protection, see "[AUTOTITLE](/code-security/secret-scanning/introduction/supported-secret-scanning-patterns#supported-secrets)." +Push protection has some limitations. For more information, see "[AUTOTITLE](/code-security/secret-scanning/troubleshooting-secret-scanning-and-push-protection/troubleshooting-secret-scanning#push-protection-limitations)." + ## How push protection works Push protection works: diff --git a/content/code-security/secret-scanning/troubleshooting-secret-scanning-and-push-protection/troubleshooting-secret-scanning.md b/content/code-security/secret-scanning/troubleshooting-secret-scanning-and-push-protection/troubleshooting-secret-scanning.md index 554728e9dc17..67bd7665e2e2 100644 --- a/content/code-security/secret-scanning/troubleshooting-secret-scanning-and-push-protection/troubleshooting-secret-scanning.md +++ b/content/code-security/secret-scanning/troubleshooting-secret-scanning-and-push-protection/troubleshooting-secret-scanning.md @@ -38,4 +38,5 @@ If your secret is in the supported list, there are various reasons why push prot * The version of your secret may be old. {% data reusables.secret-scanning.push-protection-older-tokens %} * The push may be too large, for example, if you're trying to push thousands of large files. A push protection scan may time out and not block a user if the push is too large. {% data variables.product.prodname_dotcom %} will still scan and create alerts, if needed, after the push. * If the push results in the detection of over five new secrets, we will only show you the first five (we will always show you a maximum of five secrets at one time). -* If a push contains over 1,000 existing secrets (that is, secrets for which alerts have already been created), push protection will not block the push. +* If a push contains over 1,000 existing secrets (that is, secrets for which alerts have already been created), push protection will not block the push. {% ifversion fpt or ghec %} +* If a push in a public repository is larger than 50 MB, push protection will skip it and won't scan it.{% endif %} From 913668772339137e508e6d198503cf9129fd03cf Mon Sep 17 00:00:00 2001 From: docs-bot <77750099+docs-bot@users.noreply.github.com> Date: Wed, 11 Dec 2024 08:36:08 -0800 Subject: [PATCH 2/2] Update audit log event data (#53574) --- src/audit-logs/lib/config.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/audit-logs/lib/config.json b/src/audit-logs/lib/config.json index 33c021c99d56..33c6e070be96 100644 --- a/src/audit-logs/lib/config.json +++ b/src/audit-logs/lib/config.json @@ -3,5 +3,5 @@ "apiOnlyEvents": "This event is not available in the web interface, only via the REST API, audit log streaming, or JSON/CSV exports.", "apiRequestEvent": "This event is only available via audit log streaming." }, - "sha": "2c40dff92f97e4efcefcfd98ed9e6c9f3d69284b" + "sha": "1b079a4c67a6c2eecccbef1d2d465dd62bc2248b" } \ No newline at end of file