Skip to content

ci(docs): fail the build on broken links and anchors - #81

Merged
krassx merged 1 commit into
mainfrom
ci/fail-on-broken-links
Oct 8, 2026
Merged

krassx merged 1 commit into
mainfrom
ci/fail-on-broken-links

Conversation

@krassx

@krassx krassx commented Oct 8, 2026

Copy link
Copy Markdown
Contributor

Finding #6 of the 2026-10-07 public-repo review: onBrokenLinks: 'warn' meant CI could not catch dead internal links (common /sdk/<platform>/ URLs 404'd in production).

The 404s themselves were fixed by #77 (client redirects). I checked the live site: all 9 /sdk/<platform>/ roots and the old Android v7 paths now answer 200, and every docs link in the website repo's main resolves.

This PR

onBrokenLinks and onBrokenAnchors → 'throw'.

Verified

  • The current site builds clean with both set to throw (0 broken links, 0 broken anchors), so this is free today.
  • It actually bites: a planted broken link and, separately, a planted broken anchor each make npm run build exit 1 (probe reverted).
  • Also protects the agent-skills sync PRs: a plugin skill with a dead link now fails that job's build step and the PR opens as a draft.

🤖 Generated with Claude Code

onBrokenLinks/onBrokenAnchors were 'warn', so CI could not catch a dead
internal link (the review found common /sdk/<platform>/ URLs returning 404
with nothing flagging it). The site currently has none, so switching to
'throw' costs nothing. Verified that the build exits 1 for a planted broken
link and for a planted broken anchor.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Change-Id: Ied97ba3470257049131349b1b44c9589372b7217
@krassx
krassx merged commit b172115 into main Oct 8, 2026
1 check passed
@krassx
krassx deleted the ci/fail-on-broken-links branch October 8, 2026 14:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant