External Links Checker using Lychee #1757
Closed
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
khadni
requested review from
dwightjl,
aelmanaa and
thedriftofwords
as code owners
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.
This PR updates the external links checker using Lychee.
Error handling: To avoid false positives, HTTP 403 (Forbidden), 429 (Too Many Requests), and 406 (Not Acceptable) errors are not considered failures, acknowledging rate limits, access controls, and content negotiation issues.
Immediate reporting: A Markdown report of the link check results is generated in the workflow's summary to access identified issues, facilitating prompt corrections quickly.
GitHub Token Configuration: To enhance the workflow's efficiency in verifying GitHub URLs, we utilize the
secrets.GITHUB_TOKENfor authentication. It mitigates rate-limiting issues encountered when fetching a high volume of GitHub URLs.Note: While the GITHUB_TOKEN provides sufficient privileges for accessing URLs within the scope of this repository, it does not extend to external repositories. In future scenarios where the workflow needs to access a broader range of GitHub URLs beyond this repository, we'll consider leveraging a Personal Access Token to bypass rate limits more effectively.