fix(ci): prevent duplicate CI runs on main branch pushes#20
Conversation
CI now runs on PRs targeting main and pushes to non-main branches. Release workflow already covers build+test on main pushes. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Pushing to a branch with an open PR triggered CI twice — once via push and once via pull_request. CI only needs the PR trigger; Release handles main pushes. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5b0c4fe978
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| on: | ||
| push: | ||
| branches: [main] | ||
| branches-ignore: [main] |
There was a problem hiding this comment.
Changing push to branches-ignore: [main] means every same-repo topic branch now triggers this workflow on push, while the existing pull_request trigger still runs for PRs targeting main. In the normal flow here, once feature/foo has an open PR, each new commit will enqueue two identical build-and-test runs instead of one. Before this change only the pull_request run fired, so this actually introduces duplicate CI usage for active PRs rather than removing it.
Useful? React with 👍 / 👎.
1 participant
Summary
branches-ignore: [main]instead ofbranches: [main]for push triggersTest plan
🤖 Generated with Claude Code