Skip to content

Commit 0cb52dc

Browse files
authored
Remove expiration tags from "About secret scanning" (#55178)
1 parent 591730c commit 0cb52dc

File tree

1 file changed

+0
-4
lines changed

1 file changed

+0
-4
lines changed

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

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -24,12 +24,8 @@ shortTitle: Secret scanning
2424

2525
{% data variables.product.prodname_secret_scanning_caps %} is a security feature that helps detect and prevent the accidental inclusion of sensitive information such as API keys, passwords, tokens, and other secrets in your repository. When enabled, {% data variables.product.prodname_secret_scanning %} scans commits in repositories for known types of secrets and alerts repository administrators upon detection.
2626

27-
<!-- expires 2025-04-04 -->
28-
2927
{% data variables.product.prodname_secret_scanning_caps %} scans your entire Git history on all branches present in your {% data variables.product.prodname_dotcom %} repository for secrets, even if the repository is archived. {% data variables.product.prodname_dotcom %} will also periodically run a full Git history scan for new secret types in existing content in {% ifversion fpt or ghec %}public repositories{% else %}repositories with {% data variables.product.prodname_GH_secret_protection %} enabled{% endif %} where {% data variables.product.prodname_secret_scanning %} is enabled when new supported secret types are added.
3028

31-
<!-- end expires 2025-04-04 -->
32-
3329
{% data reusables.secret-scanning.what-is-scanned %}
3430

3531
{% ifversion ghas-products %}{% ifversion secret-risk-assessment %}

0 commit comments

Comments
 (0)