ci(docs): add link checker to existing CI to prevent broken docs links#6570
Open
zyzzmohit wants to merge 1 commit intopipe-cd:masterfrom
Open
ci(docs): add link checker to existing CI to prevent broken docs links#6570zyzzmohit wants to merge 1 commit intopipe-cd:masterfrom
zyzzmohit wants to merge 1 commit intopipe-cd:masterfrom
Conversation
Signed-off-by: zyzzmohit <mohitray949@gmail.com>
Contributor
Ayushmore1214
left a comment
Ayushmore1214
left a comment
There was a problem hiding this comment.
Nice work @zyzzmohit Looks good to me!
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
2 participants
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.
Fixes #6549
Adds a lightweight link-checking step using
lychee-actionto the existing CI workflow that runs only when docs or README files change. It relies on a custom.lychee.tomlconfiguration to ignore localhost, social networks, active repository edit links, and Hugo's internal relative routing paths to avoid false positives.The action is pinned to its latest SHA (
8646ba30) equivalent tov2.8.0following the repository's existing security conventions.Does this PR introduce a user-facing change?: