Skip to content

Don't fail the link check on timeouts - #41

Merged
oalders merged 1 commit into
mainfrom
accept-timeouts
Nov 3, 2026
Merged

oalders merged 1 commit into
mainfrom
accept-timeouts

Conversation

@oalders

@oalders oalders commented Nov 2, 2026

Copy link
Copy Markdown
Member

The first scheduled link check opened #40 for two timeouts (gnu.org license pages) with 0 errors. lychee exits non-zero on timeouts, which is what triggers the issue.

Sets accept_timeouts = true in lychee.toml (applies to make linkcheck, PR runs and the weekly run). Timeouts still appear in the summary; lychee only exits 0 when nothing else failed, so real 404s and other errors still open an issue / fail the PR.

Verified locally with lychee 0.24.2: a timed-out link is reported and the exit code is 0.

Closes #40

🤖 Generated with Claude Code · Opus 5.5

A slow host is not a dead link. lychee still lists timeouts in its
summary, but exits 0 when nothing else failed, so the weekly run no
longer opens a broken-links issue for them.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@oalders
oalders merged commit 0d60250 into main Nov 3, 2026
2 checks passed
@oalders
oalders deleted the accept-timeouts branch November 3, 2026 00:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Broken links report

1 participant