chore(ci): run CI only on pull requests targeting main - #104
Conversation
CI was triggered on both `push` to `main` and `pull_request` against `main`, so every merge ran the same matrix twice. Nothing is pushed directly to `main` except merges, and `release.yml` already re-runs the full lint/typecheck/format/build/test suite on each push to `main`, so the push trigger added no signal and only burned Actions minutes. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YRkjpsg8UyhP7a9sYLHmss
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe CI workflow no longer runs on direct pushes to ChangesCI trigger update
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to CI will run for pull requests targeting main rather than duplicate runs after merges, while the post-merge release workflow remains triggered on main. No merge-blocking risk is currently identified. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Description
ci.ymlwas triggered on bothpushtomainandpull_requestagainstmain, so every merge ran the same 2-node matrix twice — once for the PR, once for the resulting push — for identical commits.On top of that,
release.ymlalready runs the fulllint/typecheck/format:check/build/testsuite on every push tomainbefore handing over to changesets, so the push-triggered CI run was doubly redundant.This PR drops the
pushtrigger fromci.yml, leavingpull_request: branches: [main]. Nothing is pushed directly tomainexcept merges, so no commit loses coverage:release.ymlruns the same checks onmain.A comment in the workflow records why the push trigger is intentionally absent.
Related issue
N/A
Type of change
Checklist
npm run build) — no source changesnpm run lint) — no source changesnpm run format:check)How to test
CI / buildrun per Node version (22, 24), and no duplicate run appears in the Actions tab.CIworkflow run is created for the push tomain, and thatReleasestill runs its lint/typecheck/format/build/test steps.CI / buildis configured as a required status check onmainin branch protection, it stays satisfied — the checks still report on the PR head, which is what protection evaluates.🤖 Generated with Claude Code
https://claude.ai/code/session_01YRkjpsg8UyhP7a9sYLHmss
Generated by Claude Code
Summary by CodeRabbit