Narrow lychee blog exclude to 2015-2018 archive (closes #36)#41
Merged
Conversation
The site-health workflow previously skipped all of _site/blog/, which turned off link checking for every blog post past or present — meaning new posts wouldn't catch broken links either. Narrow the exclude to: - _site/blog/201[5-8] (the historical posts where ~30 dead links live; triaging decade-old archival content isn't worth the effort) - _site/blog/index.html (the index aggregates every post's links, so it'd surface the same 2015-2018 errors) Posts from 2019 onward get full lychee coverage going forward. New posts catch new rot. Local: 89 OK, 0 errors, 714 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
2 participants
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.
Closes #36.
Summary
The
site-health.ymlworkflow currently passes--exclude-path _site/blogto lychee, which skipped every blog post — past, present, and future. That means any new blog post with a broken link wouldn't be caught either.Narrow the exclude to just the legacy archive:
_site/blog/201[5-8]— historical posts where the ~30 known dead links live; triaging decade-old archival content isn't a good ROI_site/blog/index.html— the blog index aggregates every post's links, so it'd surface the same 2015–2018 errorsPosts from 2019 onward now get full link coverage. New posts catch new rot, which is what the link checker is actually for.
Test plan
bundle exec jekyll buildcleanlychee --config ./lychee.toml --no-progress --root-dir _site --exclude-path '_site/blog/201[5-8]' --exclude-path '_site/blog/index\.html' _site→ 89 OK, 0 errors locally (was 84 OK with the broader exclude; the +5 OK are 2019/2020 post links that are now in scope)site-healthpasses on the PRNotes
_posts/source, only on built_site/, so fixing a single legacy link won't trigger a sea of failures from the others).https://claude.ai/code/session_01S5QXfkxZBNSAf2Y1XAD8H7
Generated by Claude Code