Repository navigation
package-ci: a notes-only pull request skips the gate, the check still passes - #19
Merged
Merged
Conversation
…till passes A step right after the checkout lists the pull request's files (the compare API, contents: read). When every one is Markdown that is not the handbook or a README and that no other file in the package names, every later step is skipped: the job runs and passes, so the required check verify / verify reports success. A workflow-level paths filter would leave that check pending forever. The filter is a step, not a job of its own, so a code change still waits for a runner only once. Releases, dispatches, 300 files or more, or a failed compare run the whole gate. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
1 participant
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.
The package gate (
verify / verify) now skips its heavy steps when a pull request changes only notes.Rule. Every changed file (and every renamed file's old name) is Markdown that is not
<name>-handbook.md(the zip ships it) and not aREADME.md(suites read them), and that no non-Markdown file in the package names (a suite that readsCLAUDE.mdorHANDOFF.mdnames it; so does aZIP_EXTRArow). Releases, dispatches, a compare call that fails or a PR of 300 files or more run the whole gate.Why a step, not a separate job or a workflow
pathsfilter. A skipped workflow leaves the required check pending forever. A separate filter job would make every code PR wait in the runner queue twice. As a step, the job still runs and passes, so the required check reports success, and a code change waits for a runner once.Checked offline against the package checkouts with a stand-in
gh: replacerHANDOFF.mdskips; replacerCLAUDE.md, photo-auditorCLAUDE.md(its suite reads it), krea-2 handbook,suite.py, a laneNOTES.mdits build reads, and character-creatorHANDOFF.md(named in its builder) all run.Measured effect (last 48 h): 4 of 137 package PRs were Markdown-only, so this saves a few gate runs a day; the queue fix is elsewhere (runner group, capacity).
🤖 Generated with Claude Code