Repository navigation
ci: run linkspector on pull requests to release branches - #32131
Merged
Merged
Conversation
The docs link check only ran on pull requests to main, and its weekly run only checks main. A backport to release/2.39 brought over a link to main's docs layout that doesn't exist on 2.39; no check saw it, and the docs publish has refused to build 2.39 since. Running the same check on pull requests to release/** catches that before merge. Pull requests use the workflow from the branch they target, so this has to be backported to each supported release branch to take effect there. Assisted-by: AI
nickvigilante
enabled auto-merge (squash)
November 17, 2026 18:06
nickvigilante
had a problem deploying
to
docs-preview
November 18, 2026 14:58 — with
GitHub Actions
Failure
This branch had an error being deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The docs link check (Linkspector, in
weekly-docs.yaml) only runs on pull requests tomain, and its weekly scheduled run only checksmain. Pull requests torelease/**never get it. That let #31796, a backport torelease/2.39, merge with a link toadmin/workspaces/devcontainers/customizing-dev-containers.md,main's layout for that page; on 2.39 the page is still underuser-guides/devcontainers/. No check flagged it, and the docs publish has refused to build 2.39 since 2026-11-09 because of it.This adds
release/**to thepull_requestbranches, so the same check runs on backports. On pull requests Linkspector only checks the Markdown files the PR changes (filter_mode: file), so a backport pays only for its own files. The Slack notification still fires only for the scheduled run.A pull request runs the workflow from the branch it targets, so this only takes effect on a release branch once it's backported there. It should be cherry-picked to each release branch that still takes docs backports (at least 2.39, 2.38 and 2.37).
actionlintreports the workflow clean.🤖 Built with AI assistance.