Skip to content

CI: consolidate lychee URL exclusions into .lycheeignore - #65

Merged
rivassec merged 1 commit into
mainfrom
lychee-config-consolidation
Sep 12, 2026
Merged

rivassec merged 1 commit into
mainfrom
lychee-config-consolidation

Conversation

@rivassec

Copy link
Copy Markdown
Owner

Backlog item 10 - the consolidation decision, implemented as: keep both lychee layers, share one exclusion config.

  • Deploy's per-PR gate (built HTML) and the weekly link-rot scan (source markdown) serve different roles and both stay.
  • URL exclusions now live only in .lycheeignore (lychee reads it automatically - verified empirically in both contexts): the deploy-only patterns (web.archive.org, hrw.org, the vendored tool page) moved in alongside the existing ones (LinkedIn/X, placeholders, Pelican syntax).
  • --exclude-path flags stay inline in deploy.yml: the ignore file holds URL regexes only.

Verified locally (full deploy sequence: build -> pagefind -> lychee)

5799 Total | 296 Unique | 0 Errors | 26 Excluded - identical coverage to the previous inline flags, one config file to maintain.

One source of truth for both lychee layers (deploy's per-PR gate on
built HTML + the weekly link-rot scan of source markdown): lychee
reads .lycheeignore automatically, so deploy.yml's inline --exclude
URL flags move there. Path exclusions (--exclude-path) stay inline
since the ignore file holds URL patterns only.

Dress-rehearsed the full deploy sequence locally (build -> pagefind ->
lychee on output HTML): 5799 links, 0 errors, 26 excluded.
@rivassec
rivassec merged commit d6b7ffb into main Sep 12, 2026
17 checks passed
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.

1 participant