Repository navigation
ci: run the test suite and coverage gate on pull requests - #31
Merged
Merged
Conversation
Tests and the 100% coverage gate previously ran only after merging to main, so pull requests were gated on the docs build alone. The new Tests workflow runs `npm run coverage` on every pull request and checks that each published entry point imports by package name. Co-Authored-By: Claude Opus 5.5 <[email protected]>
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
1 participant
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.
Tests and the 100% coverage gate ran only after merging to
main, so pull requests were gated on the docs build alone. #30 was verified locally, not by CI. This adds a Tests workflow, modelled on bloxwap/hyperliquid'stests_offline, that runs on every pull request:npm run coverage, the same command contributors run. It builds icons, WASM and TypeScript, runs the suite, and fails if any file drops below 100% line/branch/function coverage.exportssubpath must import by package name in plain Node. The tests importdist/directly, so a broken exports map would otherwise pass.It has no path filter, so it can be made a required status check without blocking docs-only PRs. Making it required is a branch-protection setting; this PR doesn't change it.
🤖 Generated with Claude Code