Skip to content

Commit 09daa42

Browse files
committed
ci: stop firing unity-tests/python-tests twice for beta and main pushes
A push to beta (or main) that touches MCPForUnity/** or Server/** triggers the test workflow via two paths: push to beta ─┬─► unity-tests.yml (direct push trigger, branches: ["**"]) │ └─► beta-release.yml ──workflow_call──► unity-tests.yml Both invocations land in GitHub's auto-generated concurrency group `unity-tests-refs/heads/beta`, so the later one cancels the earlier with the noisy "Canceling since a higher priority waiting request for unity-tests-refs/heads/beta exists" annotation. The cancelled run shows red on the Actions page even though the workflow_call sibling completed fine. Switch the direct push trigger to `branches-ignore: [beta, main]` on both unity-tests.yml and python-tests.yml. Coverage on those branches is still delivered through workflow_call from beta-release.yml / release.yml; we just stop firing a duplicate run that gets killed by concurrency. PR checks, feature-branch pushes, and manual workflow_dispatch invocations are unaffected.
1 parent a384c7c commit 09daa42

2 files changed

Lines changed: 12 additions & 2 deletions

File tree

.github/workflows/python-tests.yml

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,11 @@ name: Python Tests
22

33
on:
44
push:
5-
branches: ["**"]
5+
# Exclude beta and main: those branches re-trigger this workflow via
6+
# workflow_call from beta-release.yml / release.yml. Without the exclusion,
7+
# a push to beta that touches Server/** fires this workflow twice for the
8+
# same SHA, and GitHub auto-cancels the duplicate.
9+
branches-ignore: [beta, main]
610
paths:
711
- Server/**
812
- .github/workflows/python-tests.yml

.github/workflows/unity-tests.yml

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,13 @@ on:
1010
required: false
1111
default: ""
1212
push:
13-
branches: ["**"]
13+
# Exclude beta and main: those branches re-trigger this workflow via
14+
# workflow_call from beta-release.yml / release.yml. Without the exclusion,
15+
# a push to beta that touches MCPForUnity/** fires this workflow twice
16+
# for the same SHA, and GitHub's auto-generated concurrency group
17+
# (`unity-tests-refs/heads/beta`) cancels the older run with the noisy
18+
# "higher priority waiting request" annotation.
19+
branches-ignore: [beta, main]
1420
paths:
1521
- TestProjects/UnityMCPTests/**
1622
- MCPForUnity/Editor/**

0 commit comments

Comments
 (0)