fix(ci): don't double-trigger CI workflow on branches with open PRs #27
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/ci-no-double-trigger"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Previously
on.push.branches: ["**"]fired on every branch push, andon.pull_requestfired on the same push when it was associated withan open PR — running the same job twice. Restrict push triggers to
master so feat branches only run CI via their PR.
Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com
Automated review by pr-reviewer v0.17.0 | Safety Check | Claude Sonnet 4 | tracking id
r-e4b91b-082e03This is an AI-generated review and may contain mistakes.
Status: ✅ Completed
✅ Verdict: LGTM — This is a standard CI optimization to prevent duplicate workflow runs - no safety concerns.
Complexity: trivial
This change restricts CI workflow triggers to only run on pushes to master branch, while still running on all pull requests. This is a common pattern to avoid duplicate CI runs when a branch has an open PR (since the PR trigger would already run the workflow). The change is straightforward and poses no safety risks.
2ec0a7342be3c0ffddd6