Repository navigation
ci: check every link in the Markdown files [PANL-014] - #7
Merged
Merged
Conversation
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Bihc4e3Pg6Ago5K1xfMbe5
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Context
The review panel's documentation engineer found no link or docs checks in CI, a core part of the role. This adds a link check that runs on every pull request, every push to main, and weekly. Ticket: PANL-014.
Changes
One new workflow file,
.github/workflows/links.yml, using the lychee action. It fails the build on a broken link. Rate-limit answers (429) are not treated as broken, and LinkedIn is skipped because it blocks bots. No existing file changes.🤖 Generated with Claude Code
https://claude.ai/code/session_01Bihc4e3Pg6Ago5K1xfMbe5