Why:
The enterprise secret scanning setup guide links to a section that does not exist on the validity checks page. The link is inside the secret-scanning-validity-check-partner-patterns version block, so affected readers are sent to a nonexistent anchor instead of the instructions for enabling validity checks.
What article on docs.github.com is affected?
Configure secret scanning for an enterprise
What part(s) of the article would you like to see updated?
- In
content/code-security/how-tos/secure-at-scale/configure-enterprise-security/configure-specific-tools/configure-secret-scanning.md:64, change the link fragment from #about-validity-checks to #enabling-validity-checks.
- The target article is
content/code-security/how-tos/secure-your-secrets/customize-leak-detection/enable-validity-checks.md, whose relevant heading is ## Enabling validity checks at line 26. It has no heading or rendered ID for #about-validity-checks.
The expected outcome is that the link opens the existing “Enabling validity checks” section without changing the surrounding version gate or instructions.
Additional information
I reproduced the mismatch by comparing the source fragment with the target article’s rendered headings. I found no existing issue or pull request covering this exact link. This is a content-only correction; no generated, translated, workflow, or site-code files are involved.
Validation after the change should include:
npm run lint-content -- --paths content/code-security/how-tos/secure-at-scale/configure-enterprise-security/configure-specific-tools/configure-secret-scanning.md
npm test -- --no-file-parallelism --maxWorkers=1 src/content-render/tests/render-changed-and-deleted-files.ts
npm run build
Why:
The enterprise secret scanning setup guide links to a section that does not exist on the validity checks page. The link is inside the
secret-scanning-validity-check-partner-patternsversion block, so affected readers are sent to a nonexistent anchor instead of the instructions for enabling validity checks.What article on docs.github.com is affected?
Configure secret scanning for an enterprise
What part(s) of the article would you like to see updated?
content/code-security/how-tos/secure-at-scale/configure-enterprise-security/configure-specific-tools/configure-secret-scanning.md:64, change the link fragment from#about-validity-checksto#enabling-validity-checks.content/code-security/how-tos/secure-your-secrets/customize-leak-detection/enable-validity-checks.md, whose relevant heading is## Enabling validity checksat line 26. It has no heading or rendered ID for#about-validity-checks.The expected outcome is that the link opens the existing “Enabling validity checks” section without changing the surrounding version gate or instructions.
Additional information
I reproduced the mismatch by comparing the source fragment with the target article’s rendered headings. I found no existing issue or pull request covering this exact link. This is a content-only correction; no generated, translated, workflow, or site-code files are involved.
Validation after the change should include: