Skip to content

Commit f69dfd8

Browse files
authored
Set expectations about time needed for alerts to be deleted once the corresponding custom pattern is removed (#58875)
1 parent 5540f12 commit f69dfd8

File tree

1 file changed

+2
-0
lines changed
  • content/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/custom-patterns

1 file changed

+2
-0
lines changed

content/code-security/secret-scanning/using-advanced-secret-scanning-and-push-protection-features/custom-patterns/managing-custom-patterns.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -39,6 +39,8 @@ When you remove a custom pattern, {% data variables.product.github %} gives you
3939
1. Review the confirmation, and select a method for dealing with any open alerts relating to the custom pattern.
4040
1. Click **Yes, delete this pattern**.
4141

42+
If you choose to close the alerts when removing a custom pattern, you need to be aware that the deletion process happens asynchronously in the background. For custom patterns that have generated a high volume of alerts (thousands or more), the deletion process may take several minutes to hours to complete. You can continue working while the process completes.
43+
4244
## Enabling push protection for a custom pattern
4345

4446
You can enable {% data variables.product.prodname_secret_scanning %} as a push protection for custom patterns stored at the enterprise, organization, or repository level.

0 commit comments

Comments
 (0)