ci: add tool template to validate-templates matrix#14
Merged
Conversation
The `tool` template (templates/tool/, added in v2.0.0) was only covered by the `init --template tool` unit test, not the CI matrix that builds each template end-to-end (scaffold -> pack -> install tgz -> astro build). Add it as the 6th matrix entry so it is exercised like the others. Verified locally by mirroring the matrix step: scaffold a temp project with `init --template tool`, `npm pack`, install the tgz into site/, and `npm run build` -- builds clean. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
What
Adds
toolto thevalidate-templatesmatrix in.github/workflows/ci.yml, so the 6th template (added in v2.0.0) is built end-to-end in CI like the other five.Why
templates/tool/was covered only by theinit --template toolunit test intests/cli.test.mjs— never by the matrix job that scaffolds each template, packs the theme, installs the tarball, and runsastro build. This closes that gap with no other matrix growth.Verification
Mirrored the matrix step locally before pushing:
node cli/init.mjs init --template tool --dry-run— plan is correctinit --template tool→npm pack→ install the.tgzintosite/→npm run buildastro buildcompletes clean (1 page built)The new
validate-templates (tool)job should pass in CI here.Constraints honored (org Actions rules)
push/pull_requesttriggers unchangedruns-on: ubuntu-latestunchangedconcurrencyblock intact🤖 Generated with Claude Code