Skip to content

Add CI to run the setup-repo test suites - #4

Merged
jonnyspicer merged 1 commit into
mainfrom
ci/run-setup-repo-tests
Jul 15, 2026
Merged

jonnyspicer merged 1 commit into
mainfrom
ci/run-setup-repo-tests

Conversation

@jonnyspicer

Copy link
Copy Markdown
Contributor

The repo had no workflow exercising the setup-repo scaffolding tests, so regressions in the assets, the scaffold engine, or the CI/asset validators could merge undetected (flagged in PR #1's final review).

What this adds

.github/workflows/setup-repo-tests.yml — on push to main and every PR:

  • installs the test tools with uv (astral-sh/setup-uv + uv pip install --system pyyaml ruff pytest), matching the org Python standard the skill itself scaffolds;
  • runs all three suites: test-python-assets.sh, test-ci-assets.sh, and the end-to-end test-scaffold.sh (which now runs real ruff/pytest against a scaffolded temp repo, since the tools are installed).

Notes

  • run: steps are static bash with no ${{ github.event.* }} interpolation — no injection surface.
  • All three suites pass locally.

🤖 Generated with Claude Code

Nothing in this repo exercised the scaffolding tests, so engine/asset regressions
could slip through. Add a workflow that installs the test tools via uv (matching
the org Python standard) and runs the three setup-repo suites (python-assets,
ci-assets, scaffold e2e) on push to main and every PR.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@jonnyspicer
jonnyspicer merged commit 6982c80 into main Jul 15, 2026
2 checks passed
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