Skip to content

ci: skip unit and integration suites on changeset release PRs - #831

Merged
cameri merged 1 commit into
mainfrom
ci/skip-heavy-on-release-pr
Oct 15, 2026
Merged

cameri merged 1 commit into
mainfrom
ci/skip-heavy-on-release-pr

Conversation

@chappie-daemon

Copy link
Copy Markdown
Collaborator

What

On changeset release PRs (changeset-release/main), the two long test jobs — Unit Tests And Coverage and Integration Tests and Coverage — are now skipped. Lint, build check, commitlint and the changeset gate still run.

Why

A release PR only touches manifests and changelogs (measured on #827: zero files under src/; diff = package.json, pnpm-lock.yaml, changelogs, changeset files). The code it carries is identical to what just finished green on main, and the squash-merge fires the full checks.yml suite on main via the push trigger anyway — so the release-PR test run re-proves nothing and costs ~20 min of runner time per release. github.head_ref is empty on push events, so the gate is a no-op on main pushes and container publishing is untouched.

Same gate shape changeset-check already uses (github.head_ref != 'changeset-release/main').

Verification

  • YAML parses; all 8 job if expressions validated against the workflow's own needs/outputs graph.
  • On a release PR: lint/build/commitlint green, both test jobs skipped — required checks still report (skipped counts as satisfied for these two), so branch protection still passes the merge button.
  • On ordinary PRs and main pushes: expression evaluates unchanged (head_ref never equals changeset-release/main).

Loading
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.

3 participants