Skip to content

ci: install typos + lychee (Tier-2 quality)#130

Merged
mastermanas805 merged 2 commits into
masterfrom
ci/tier2-typos-lychee
May 21, 2026
Merged

ci: install typos + lychee (Tier-2 quality)#130
mastermanas805 merged 2 commits into
masterfrom
ci/tier2-typos-lychee

Conversation

@mastermanas805
Copy link
Copy Markdown
Member

Summary

  • typos — fast spell-checker (3s run)
  • lychee — broken-link checker for markdown + HTML, warn-only initially

100% free for public repos. Both run on PRs + master + weekly schedule.

🤖 Generated with Claude Code

@mastermanas805
Copy link
Copy Markdown
Member Author

Status note: typos is finding real spell-check issues in the existing codebase — that's the workflow doing its job on first install. lychee (links) is green (warn-only as configured).

This PR is intentionally left open as a baseline-visibility PR. Either:

  1. Fix the typos in a follow-up PR (or add a .typos.toml allowlist), then re-run CI here and merge, or
  2. Merge with admin-bypass to land the workflow infrastructure now, then triage typos separately.

mastermanas805 and others added 2 commits May 22, 2026 00:04
typos (crate-ci): fast Rust-based spell-checker for source + docs
lychee: broken-link checker for markdown + HTML

100% free for public repos. Both run in <1min.

lychee starts with fail=false (warn-only) so first runs don't block
merges if the existing markdown has broken links. Flip to fail=true
after baseline is clean.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Surface spelling findings without blocking CI on existing baseline.
Lychee was already warn-only; this aligns typos with the same posture.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@mastermanas805 mastermanas805 force-pushed the ci/tier2-typos-lychee branch from d4ff6be to 5e6f086 Compare May 21, 2026 18:34
@mastermanas805 mastermanas805 merged commit 17135b4 into master May 21, 2026
9 of 11 checks passed
@mastermanas805 mastermanas805 deleted the ci/tier2-typos-lychee branch May 21, 2026 18:39
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