CI: consolidate lychee URL exclusions into .lycheeignore - #65
Merged
Merged
Conversation
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.
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
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.
Backlog item 10 - the consolidation decision, implemented as: keep both lychee layers, share one exclusion config.
.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-pathflags 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.