Why:
Four CodeQL articles still link to the legacy advanced-setup route instead of the current article path. The legacy route resolves through a redirect, but the repository guidance treats links that work only through redirects as stale links. Updating the source paths removes the redirect hop and keeps the permissions text aligned with the current CodeQL documentation structure.
What article on docs.github.com is affected?
The following four CodeQL articles contain the same stale route in their permissions frontmatter:
content/code-security/concepts/code-scanning/codeql/codeql-for-compiled-languages.mdcontent/code-security/how-tos/find-and-fix-code-vulnerabilities/manage-your-configuration/codeql-for-compiled-languages.mdcontent/code-security/reference/code-scanning/codeql/build-options-for-compiled-languages.mdcontent/code-security/reference/code-scanning/workflow-configuration-options.md
What part(s) of the article would you like to see updated?
Replace:
/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/configuring-advanced-setup-for-code-scanning
with:
/code-security/how-tos/find-and-fix-code-vulnerabilities/configure-code-scanning/configuring-advanced-setup-for-code-scanning
The current destination is content/code-security/how-tos/find-and-fix-code-vulnerabilities/configure-code-scanning/configuring-advanced-setup-for-code-scanning.md, and its frontmatter explicitly lists the old route as a redirect. No product wording, permissions behavior, or generated API data needs to change.
Additional information
I verified that the current destination exists and that the old route is a legacy redirect. I found no existing issue or pull request covering these four source occurrences. This is a content-only link 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/concepts/code-scanning/codeql/codeql-for-compiled-languages.md content/code-security/how-tos/find-and-fix-code-vulnerabilities/manage-your-configuration/codeql-for-compiled-languages.md content/code-security/reference/code-scanning/codeql/build-options-for-compiled-languages.md content/code-security/reference/code-scanning/workflow-configuration-options.md
npm test -- --no-file-parallelism --maxWorkers=1 src/content-render/tests/render-changed-and-deleted-files.ts
npm run build
Why:
Four CodeQL articles still link to the legacy advanced-setup route instead of the current article path. The legacy route resolves through a redirect, but the repository guidance treats links that work only through redirects as stale links. Updating the source paths removes the redirect hop and keeps the permissions text aligned with the current CodeQL documentation structure.
What article on docs.github.com is affected?
The following four CodeQL articles contain the same stale route in their
permissionsfrontmatter:content/code-security/concepts/code-scanning/codeql/codeql-for-compiled-languages.mdcontent/code-security/how-tos/find-and-fix-code-vulnerabilities/manage-your-configuration/codeql-for-compiled-languages.mdcontent/code-security/reference/code-scanning/codeql/build-options-for-compiled-languages.mdcontent/code-security/reference/code-scanning/workflow-configuration-options.mdWhat part(s) of the article would you like to see updated?
Replace:
with:
The current destination is
content/code-security/how-tos/find-and-fix-code-vulnerabilities/configure-code-scanning/configuring-advanced-setup-for-code-scanning.md, and its frontmatter explicitly lists the old route as a redirect. No product wording, permissions behavior, or generated API data needs to change.Additional information
I verified that the current destination exists and that the old route is a legacy redirect. I found no existing issue or pull request covering these four source occurrences. This is a content-only link correction; no generated, translated, workflow, or site-code files are involved.
Validation after the change should include: