ci: Skip ClusterFuzzLite fuzzing on non-Go PRs#6591
Merged
chenrui333 merged 4 commits intoJun 26, 2026
Conversation
The ClusterFuzzLite workflow ran on every PR, including docs-only ones, wasting CI time building and running fuzzers with no Go changes. Add a dorny/paths-filter gate (matching the tester workflow) so fuzzing only runs when Go sources, go.*, the .clusterfuzzlite config, or the workflow itself change. A skip-fuzzing job reports for the other case. Signed-off-by: PePe Amengual <2208324+jamengual@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Reduces wasted CI time by gating the ClusterFuzzLite workflow so Go fuzzers only run on PRs that change Go code or fuzzing-related files, while still producing a clean workflow result for docs-only PRs.
Changes:
- Add a
dorny/paths-filter“changes” job to detect fuzz-relevant modifications. - Run the
Fuzzingjob only when the filter indicates relevant changes. - Add a
skip-fuzzingno-op job for the non-relevant-change case to keep the workflow green.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> Signed-off-by: PePe Amengual <2208324+jamengual@users.noreply.github.com>
Use the same checkout and harden-runner pins as the rest of the workflow set for the new ClusterFuzzLite gating jobs. Assisted-by: OpenAI <noreply@openai.com> Signed-off-by: Rui Chen <rui@chenrui.dev>
2 tasks
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
The
ClusterFuzzLiteworkflow triggers on every PR tomain/release-**with no path filter, so docs-only PRs (e.g. #6590) still build and run the Go fuzzers for ~10 minutes — pure wasted CI.This adds a
dorny/paths-filtergate (the same pattern thetesterworkflow uses) so fuzzing only runs when something fuzz-relevant changes:**.gogo.*.clusterfuzzlite/**.github/workflows/clusterfuzzlite.ymlA
skip-fuzzingno-op job covers the other case so the workflow still reports cleanly.Test plan
dorny/paths-filtergating intest.yml