Repository navigation
ci: skip CI and release runs for agent-only changes - #5183
Conversation
A change that touches only agent files (.agents, .claude, .codex, AGENTS.md, CLAUDE.md, skills-lock.json) no longer runs the full CI suite on its PR or on its merge, and no longer starts the release job on main or next. Contributors run pnpm check:workflow locally after editing rules, as AGENTS.md says. A push that also changes code, tooling or a changeset still runs both workflows. Shipped fast, no review.
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
|
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Why
Agent-only PRs, such as pstack syncs, ran the full CI suite (
bun check: workflow check, lint, typecheck, all tests and the slowest tests) on the PR andcheck:pushagain on the merge, plus the release job onmain, without touching any code those runs check.What changed
ci.ymlno longer lists.agents/**,.claude/**,.codex/**,AGENTS.md,CLAUDE.mdorskills-lock.jsonin itspushandpull_requestpath filters.release.yml's push trigger ignores those same paths. GitHub skips a run only when every changed file matches, so a push that also changes code or adds a changeset still releases.pnpm check:workflowstays the local gate after a rule edit, asAGENTS.mdanddocs/development/agent-skills.mdalready say, and it still runs insidebun checkwhenever CI runs for other paths.Verification
ci.ymland adds the same six aspaths-ignoreinrelease.yml..github/workflows/**, so it still runs CI.Shipped fast, no review.