ci(links): tolerate auth walls and anti-bot 403s in link checker#2
Merged
Conversation
Add lychee.toml at the repo root so the link-checker configuration is auditable in one place. Accept 403 and 429 as success (these mean "the link works but lychee cannot follow it"), follow redirects up to 5 hops, retry once on transient errors, and use a browser-shaped UA so CDN-fronted sites do not bot-block. Excludes the Private Vulnerability Reporting URL from checking. The URL is correct, but it 302-redirects to a GitHub login wall that lychee cannot follow.
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
1 participant
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.
[Add lychee.toml at the repo root so the link-checker configuration is auditable in one place. Accept 403 and 429 as success (these mean "the link works but lychee cannot follow it"), follow redirects up to 5 hops, retry once on transient errors, and use a browser-shaped UA so CDN-fronted sites do not bot-block.
Excludes the Private Vulnerability Reporting URL from checking. The URL is correct, but it 302-redirects to a GitHub login wall that lychee cannot follow.
Pull Request
What this change does
Briefly describe the change in one or two sentences.
Type of change
Important: framework content is canonical
The framework text (the six steps, the F check questions, the Y diagnostic, the in-one-sentence lines) is the published intellectual work of Sandra Robinson and is treated as canonical. Changes to the framework content itself need to be discussed in an issue first before a PR is opened.
Implementation changes (the tool, the skill instructions, the website copy, the build specs) are open to PR without prior discussion.
Checklist
](https://www.bestpractices.dev/en/projects/12980/passing/edit)