Repository navigation
CI: fuzz pull requests only when the fuzzed code changes - #10
Merged
Merged
Conversation
A Changes job lists the pull request's files and gates the expensive jobs: fuzzing runs when the code it fuzzes or the fuzz harnesses / corpus change, not for dependency or CI version bumps, and docs-only changes skip the heavy build jobs. Pushes to main, a new weekly run and manual runs do everything. A job is skipped only on an explicit "false", so if the Changes job fails, everything runs.
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.
Dependency and CI version bumps (like Renovate's PRs) no longer wait on a fuzz run.
What changes
Changesjob lists the pull request's files through the API (no third-party action) and sets flags for the jobs after it.mainafter merge and in a new weekly run.*.md,docs/,LICENSE) also skip the heavy build jobs, where the repo has any.main, the weekly schedule and manual runs still run everything.Why it can't silently skip a required check
if:reports success, so required checks don't block the merge.!cancelled() && needs.changes.outputs.x != 'false'. If the Changes job fails, or the file list can't be read, everything runs.This PR only touches
ci.yml, so its own run should already show Fuzz skipped.