Skip to content

ci: only run fuzz job on pushes to main#23

Merged
GregTheGreek merged 2 commits into
mainfrom
ci/fuzz-on-push-only
May 14, 2026
Merged

ci: only run fuzz job on pushes to main#23
GregTheGreek merged 2 commits into
mainfrom
ci/fuzz-on-push-only

Conversation

@GregTheGreek
Copy link
Copy Markdown
Owner

Summary

Fuzz currently runs on every PR push and takes ~10 minutes (10 targets x 60s each). It rarely surfaces regressions that should block a PR, but it does dominate cycle time.

Gate the job to push events on refs/heads/main so:

  • PRs: fuzz is skipped -> faster merges
  • Merge to main: fuzz still runs post-merge as a smoke sweep
  • Tag pushes: skipped (the merge commit already covered them)

If a fuzz regression slips in via a PR, the post-merge run on main will catch it within minutes; the existing pull_request checks (test, clippy, fmt, cargo-deny, gui) remain mandatory.

Test plan

  • One-line if: guard on the fuzz job, no other changes
  • After merge: confirm fuzz does not run on a subsequent PR, and does run on the merge commit push

Fuzz currently runs on every PR push and takes ~10 min for 10 targets
at 60s each, dominating PR cycle time without surfacing many real
regressions. Gate it to `push` events on `refs/heads/main` so:

* PRs no longer wait on fuzz to merge
* merged main pushes still get the post-merge fuzz sweep
* tag pushes skip (the merge commit already covered them)

Co-Authored-By: Claude
@GregTheGreek GregTheGreek marked this pull request as ready for review May 14, 2026 17:18
@GregTheGreek GregTheGreek merged commit 01b465e into main May 14, 2026
7 checks passed
@GregTheGreek GregTheGreek deleted the ci/fuzz-on-push-only branch May 14, 2026 17:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant