Repository navigation
ci: skip unit and integration suites on changeset release PRs - #831
Merged
Merged
Conversation
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
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 fullchecks.ymlsuite on main via thepushtrigger anyway — so the release-PR test run re-proves nothing and costs ~20 min of runner time per release.github.head_refis empty on push events, so the gate is a no-op on main pushes and container publishing is untouched.Same gate shape
changeset-checkalready uses (github.head_ref != 'changeset-release/main').Verification
ifexpressions validated against the workflow's own needs/outputs graph.skipped— required checks still report (skipped counts as satisfied for these two), so branch protection still passes the merge button.changeset-release/main).