Repository navigation
ci: skip full checks for draft pull requests - #3
Merged
Merged
Conversation
PerfectPan
marked this pull request as ready for review
November 3, 2026 09:02
PerfectPan
marked this pull request as draft
November 3, 2026 09:04
This was referenced Nov 3, 2026
PerfectPan
marked this pull request as ready for review
November 3, 2026 09:17
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
Summary
Apply the full-CI policy prepared in project-template #9 to the pnpm template. Ready PRs run on opened, synchronize, reopened and ready_for_review; Draft PR events skip the full check job. Preserve the existing main push trigger, pnpm check command, runtime, check name, concurrency and read-only permissions.
Keep the lightweight Review workflow active for Draft and metadata feedback. Keep both release workflows unchanged, including pr-draft: always. Update CONTRIBUTING, README and the release runbook so maintainers mark release PRs Ready before expecting full CI and distinguish skipped checks from executed tests. No dependency, lockfile, package or publishing behavior changes; no changeset is needed.
Validation
147405bebc3cc74093f88f0f791a1d8cc7d661be, the initial Draft CI run correctly skipped thecheckjob, while Draft Review actually passed all three jobs. The skipped job is not a test pass.pnpm run checkincluding 15 tests; Ready Review also passed. Checkout logs confirm merge3aa4d04a00629ac43e631d0251ff1c6827a99c92, combining current main23a8699e837e506d3ea88944df8e0c196854a01cwith the final head.Risks
GitHub reports skipped jobs as successful, even if required; maintainers must verify that the current Ready head and merge result actually executed the full check job. Read-only inspection found no active rulesets or classic branch protection on this repository; settings are unchanged. Workflow approval can still be required for GITHUB_TOKEN-created PR events. This PR does not publish packages or run the release workflows.