ci(link-check): use lychee --base-url and authenticate github.com - #172
Merged
Conversation
lychee deprecated --base in favor of --base-url; the old flag will be removed. Pass a GITHUB_TOKEN to the lychee step so github.com links are checked authenticated (5000 req/hr instead of 60), removing the repeated "unexpectedly big rate limit backoff ... Capping to 1m" warnings. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Arthurvdv
added a commit
that referenced
this pull request
Sep 5, 2026
…#173) The scheduled External link check still logged, even after #172 added a GITHUB_TOKEN: Host github.com sent an unexpectedly big rate limit backoff duration of 5m. Capping the duration to 1m instead. The warning comes from lychee's per-host adaptive rate limiter: when github.com rate-limits us it returns a multi-minute reset, which exceeds lychee's hardcoded 60s cap. The token only raises the REST API limit; plain github.com web-page checks (/blob/, /tree/, /releases, anchors) don't use the API, so a burst of concurrent requests still trips github.com's rate limit. Add .github/lychee.toml throttling only github.com (concurrency 2, 1s interval) and pass --config to it. lychee-action@v2 ships lychee v0.24.2, which supports per-host config (v0.23.0+). Other hosts are unaffected; ~30s added to a weekly job that already has fail: false. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
What
Fixes two warnings emitted by the scheduled External link check (lychee) job — not the Hugo build, which is already correct.
--baseis deprecated → renamed to--base-urlin the lychee step (the old flag "will soon be removed").Host github.com sent an unexpectedly big rate limit backoff duration of 5m. Capping the duration to 1m instead.→ lychee was crawling the site's 27 github.com links unauthenticated, tripping GitHub's 60 req/hr limit. Passingtoken: ${{ secrets.GITHUB_TOKEN }}authenticates those requests (5000 req/hr), removing the backoff.Doc comments in
link-check.yamland.lycheeignoreupdated to match the new flag name.Verification
The job runs on
schedule+workflow_dispatch. After merge (or on this branch), trigger it manually:and confirm the log no longer shows the
--base is deprecatedorrate limit backoffwarnings, and the job still reports link results.Reference (failing) run: https://github.com/ALCops/alcops.dev/actions/runs/33973902514/job/101327250177
🤖 Generated with Claude Code