Repository navigation
feat: skip the stack jobs of docs-only pull requests, when asked - #70
Merged
Merged
Conversation
`github.ci.skip_when_only` lists globs. A pull request that changes only matching paths skips the stack jobs; the commit message and drift checks still run, pushes run everything, and if the files cannot be read the jobs run. A required check on a skipped stack job is refused. GitHub only.
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.
What
A new, opt-in key:
With it,
ci.ymlgets achangesjob that reads the pull request's files from the API (no checkout, works for forks). When every file matches a glob, the stack jobs are skipped, and GitHub counts a skipped job as passed.commitsand the drift check are never gated, so the preset's required checkcommits / commitlintis always reported.code=trueand the stack jobs run.node / test (22)) is refused while the key is set, because a skipped job that calls a reusable workflow never reports its inner checks.rules:changescannot say "only these changed".Checked
npm test(485 tests, including new glob, config and CI module tests),npm run typecheck,npm run lint.repokeeper updateon a copy of repokeeper-demo-go with the key set: the generatedci.ymlpasses actionlint 1.7.7.gh: docs only gives false; a code file, a nestedsub/README.md, a failing API call or a push all give true.