fix(ci): don't double-trigger CI workflow on branches with open PRs #27

Merged
rcsheets merged 1 commit from fix/ci-no-double-trigger into master 2026-04-19 11:24:53 +00:00
Owner

Previously on.push.branches: ["**"] fired on every branch push, and
on.pull_request fired on the same push when it was associated with
an 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

Previously `on.push.branches: ["**"]` fired on every branch push, and `on.pull_request` fired on the same push when it was associated with an 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>
fix(ci): don't double-trigger CI workflow on branches with open PRs
Some checks are pending
CI / ci (pull_request) Waiting to run
2ec0a7342b
Previously `on.push.branches: ["**"]` fired on every branch push, and
`on.pull_request` fired on the same push when it was associated with
an 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>
Collaborator

Automated review by pr-reviewer v0.17.0 | Safety Check | Claude Sonnet 4 | tracking id r-e4b91b-082e03
This 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.

*Automated review by [pr-reviewer](https://git.brooktrails.org/brooktrails/pr-reviewer) v0.17.0 | Safety Check | Claude Sonnet 4 | tracking id `r-e4b91b-082e03`* *This 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.
rcsheets force-pushed fix/ci-no-double-trigger from 2ec0a7342b
Some checks are pending
CI / ci (pull_request) Waiting to run
to e3c0ffddd6
All checks were successful
CI / ci (pull_request) Successful in 1m48s
2026-04-19 11:14:40 +00:00
Compare
rcsheets merged commit 3263a8fe73 into master 2026-04-19 11:24:53 +00:00
rcsheets deleted branch fix/ci-no-double-trigger 2026-04-19 11:24:54 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
brooktrails/forgejo-runner-operator!27
No description provided.