Skip to content

feat(ci): run typecheck and all test projects on every PR - #556

Merged
Juliusolsson05 merged 1 commit into
mainfrom
feat/pr-ci-checks
Jul 17, 2026
Merged

Juliusolsson05 merged 1 commit into
mainfrom
feat/pr-ci-checks

Conversation

@Juliusolsson05

Copy link
Copy Markdown
Owner

What

One lean workflow, .github/workflows/ci.yml: a single macOS job running the repo's real gates on every PR and push to main — npm run typecheck (the only type gate in the repo), workflow-mcp package tests, and the unit / integration / renderer Vitest projects.

Why

Nothing ran on PRs before this. release.yml is workflow_dispatch-only, so merges relied entirely on local discipline in a repo whose best-documented trap is that build and tests do not type-check. The #533 merge-then-revert and PR #526 arriving with zero checks are the failure mode this closes.

Deliberately excluded

  • Packaging / signing / dual-arch verify + smoke — stay in release.yml (the structural verifier requires both arch builds).
  • npm audit — advisory drift fails PRs that changed nothing; stays in release.yml.
  • Lint (none exists by choice), coverage thresholds, required-check branch protection.

Proof

This PR is the first run of the workflow itself — the checks below are the evidence.

🤖 Generated with Claude Code

Until now nothing ran on pull requests - release.yml is manual-dispatch
only, so every merge decision rested on whoever remembered that neither
electron-vite build nor vitest type-checks. One macos job mirrors the
proven validation half of release.yml's build-app job (typecheck,
workflow-mcp tests, unit/integration/renderer). Packaging, dual-arch
verification, and npm audit deliberately stay release-only; there is no
lint job because the repo has no linter by choice.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@Juliusolsson05
Juliusolsson05 merged commit 4c5d202 into main Jul 17, 2026
1 check passed
@Juliusolsson05
Juliusolsson05 deleted the feat/pr-ci-checks branch July 17, 2026 13:16
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