Skip to content

ci: drop push:main trigger from ci and fuzz (saves ~2min/merge)#47

Merged
aksOps merged 1 commit intomainfrom
ci-trim-main-triggers
Apr 23, 2026
Merged

ci: drop push:main trigger from ci and fuzz (saves ~2min/merge)#47
aksOps merged 1 commit intomainfrom
ci-trim-main-triggers

Conversation

@aksOps
Copy link
Copy Markdown
Contributor

@aksOps aksOps commented Apr 23, 2026

Summary

Drops the redundant `push: branches: [main]` trigger from `ci.yml` and `fuzz.yml`. The PR check on `pull/N/merge` already validates the merged-state tree — re-running these workflows on `main` after a squash-merge duplicates work that already passed.

`codeql.yml` keeps its `push: main` trigger because the Security tab's default-branch code-scanning data requires a push-scoped SARIF upload.

Savings

~2 min of compute per merged PR (ci: ~1.5min, fuzz: ~30s).

Test plan

  • This PR's CI runs once on `pull_request:` — no `push:main` run should appear after merge
  • Future PRs still run ci + fuzz
  • CodeQL still runs on both push-to-main and pull_request (unchanged)

🤖 Generated with Claude Code

PR CI already validates the merged-state tree (GitHub tests
pull/N/merge). Re-running ci.yml and fuzz.yml on main after a
squash-merge adds no signal and costs ~2 min per merge.

CodeQL keeps its push:main trigger — the Security tab default-branch
data requires a push-scoped SARIF upload.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@aksOps aksOps merged commit d141cf2 into main Apr 23, 2026
15 of 16 checks passed
@aksOps aksOps deleted the ci-trim-main-triggers branch April 23, 2026 06:44
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