Skip to content

Commit 8315e6e

Browse files
committed
adding info on fixing a secret later
1 parent 295e6c7 commit 8315e6e

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -99,10 +99,12 @@ You can remove the secret from the file using the web UI. Once you remove the se
9999

100100
### Bypassing push protection for a secret
101101

102-
If {% data variables.product.prodname_dotcom %} blocks a secret that you believe is safe to push, you can allow the secret and specify the reason why it should be allowed.
102+
If {% data variables.product.prodname_dotcom %} blocks a secret that you believe is safe to push, you can allow the secret and specify the reason why it should be allowed. If you confirm a secret is real and that you intend to fix it later, you should aim to remediate the secret as soon as possible.
103103

104104
{% data reusables.secret-scanning.push-protection-allow-secrets-alerts %}
105105

106+
If you confirm a secret is real and that you intend to fix it later, you should aim to remediate the secret as soon as possible.
107+
106108
1. In the banner that appeared at the top of the page when {% data variables.product.prodname_dotcom %} blocked your commit, click **Bypass protection**.
107109
{% data reusables.secret-scanning.push-protection-choose-allow-secret-options %}
108110

0 commit comments

Comments
 (0)