Skip to content

Add CI: type-check + build on every pull request - #42

Merged
tribal2 merged 1 commit into
rotary-dev-fellowship:developfrom
Tim2investcope:ci/add-build-workflow
Aug 28, 2026
Merged

tribal2 merged 1 commit into
rotary-dev-fellowship:developfrom
Tim2investcope:ci/add-build-workflow

Conversation

@Tim2investcope

Copy link
Copy Markdown
Contributor

What's missing

The repo has no automated checks on pull requests today — `.github/` only contains `dependabot.yml`. Nothing runs a build, type-check, or lint when a PR is opened, so the only thing catching a broken contribution before merge is a maintainer noticing by hand (visible on PR #40 and #41, both showing "Checks 0").

What this adds

One new file, `.github/workflows/ci.yml`. It runs the build script that already exists in `package.json` (`astro check && astro build && node process-html.mjs`) automatically:

  • On every pull request targeting `develop`
  • On every push to `develop`
  • Manually via `workflow_dispatch`, for re-running on demand

No new tooling, no config decisions — pnpm's version is pulled from the `packageManager` field already pinned in `package.json`, and it just runs the existing script.

Verified

Ran this for real on my fork (not just locally): opened a same-repo PR to trigger the `pull_request` event, watched the Actions run complete green in 1m37s — checkout, pnpm install, `astro check`, full `astro build` all passed. Closed that verification PR once confirmed; this PR is the real one.

The repo has no automated checks on pull requests today (only
Dependabot). This adds a GitHub Actions workflow that runs the
existing `pnpm run build` script (astro check && astro build) on
every PR against develop and every push to develop, using the
pnpm version already pinned in package.json's packageManager field.

No new tooling or config decisions — just running what already
exists as an npm script automatically instead of only when someone
remembers to run it locally.
@tribal2
tribal2 merged commit 455164b into rotary-dev-fellowship:develop Aug 28, 2026
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.

2 participants