Repository navigation
ci(template): standardize ready pull request checks - #9
Merged
Merged
Conversation
PerfectPan
marked this pull request as ready for review
November 3, 2026 09:13
This was referenced Nov 3, 2026
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
Make the technology-agnostic CI example use one full-check policy: Ready pull requests run when opened, updated with new commits, reopened, or marked Ready; Draft pull requests skip the full job. Keep the existing main-push trigger and the lightweight Review workflow unchanged.
Document adoption expectations, including preserving project-specific manual triggers and release Draft flows, checking the actual executed job before merging, and keeping repository/title/body feedback available on Draft PRs. This is narrow maintenance of the workflow example and contribution policy; no separate design document is needed.
Validation
gh repo-checks repositoryandgit diff --checkpassed.actionlint1.7.12 passed for.github/workflows/ci.yml.exampleand.github/workflows/review.yml.5aa0cb5e0acc927f60c33df247bddf3c9489aef2while the PR remained Draft. The repository, title and description jobs all executed successfully. The CI example remains an inactive.examplefile with a placeholder command; this template has no real application suite, so no full-CI execution is claimed.Risks
GitHub treats a skipped job as successful, even when it is required. Draft skipping must not be mistaken for executed tests: after marking a PR Ready, review successful full checks for the current comparison before merging. The active Review workflow remains available during Draft work.
Read-only inspection found no classic protection on
mainand one disabled ruleset; this change does not configure repository settings or enforce merge protection. Downstream projects must preserve their required check names and existing necessary push/manual triggers when adopting the example. No publishing, security configuration, or unrelated workflow changes are included.