👷 Run automated tests in CI on each pull request#9
Merged
Conversation
Add a CI workflow that runs formatting, lint, type check, and the test suite on every pull request and on pushes to main. Also pin the Deno version (2.9.1) across all workflows so CI is reproducible and version bumps are deliberate.
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.
Motivation
The test suite (
test/staticalize.test.ts) only ran manually — the sole GitHub Actions workflow (publish.yaml) triggers exclusively onv*tags, so pull requests could be merged without tests, lint, formatting, or type checks ever being validated.Approach
.github/workflows/ci.yamlthat runs on everypull_requestand on pushes tomain. A singleubuntu-latestjob runs the full quality gate documented inAGENTS.md, cheapest checks first:deno fmt --check,deno lint,deno check mod.ts main.ts, thendeno test -A.2.9.1in the new workflow and across all four existingpublish.yamljobs (previously the floatingv2.x), so CI is reproducible and a Deno point-release can't silently change behavior. Bumping Deno now becomes a deliberate, reviewable change.