ci: Split CI checks by changed area#798
Conversation
Run CI checks as focused jobs behind path-based gates so pull requests avoid unrelated work while pushes keep full coverage. Add shared Node and pnpm setup, workflow concurrency, a required aggregator for skipped jobs, and scoped dashboard/eval setup. Co-Authored-By: GPT-5 Codex <codex@openai.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 275ee22. Configure here.
| "${{ needs.pack-release-artifacts.result }}"; do | ||
| if [[ "$result" != "success" && "$result" != "skipped" ]]; then | ||
| failed=1 | ||
| fi |
There was a problem hiding this comment.
Cancelled jobs fail required check
Medium Severity
The ci / required job treats cancelled the same as failure, while the workflow enables cancel-in-progress for pull requests. When a newer push cancels an in-flight run, sibling jobs often end as cancelled, so the aggregator can report a failed required status even though a newer run is still valid.
Reviewed by Cursor Bugbot for commit 275ee22. Configure here.


CI now runs as focused, path-gated jobs instead of one monolithic workflow. Pull requests run only the relevant release, skills, lint, typecheck, test, build, docs, and dashboard e2e checks, while pushes still run the full set and package artifacts.
The workflow also centralizes Node/pnpm setup in a local composite action, adds concurrency cancellation for stale PR runs, limits Playwright installation to dashboard e2e, and uses a single
ci / requiredaggregator so branch protection can accept intentionally skipped jobs without losing failure signal.After this lands, branch protection should require
ci / requiredinstead of the old monolithic CI job.