coplaydev--unity-mcp

Files

T

Shutong Wu 09daa42545 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.

2026-05-22 23:30:01 +08:00

beta-release.yml

fix: unblock beta compile and gate releases on test success (#1103 )

2026-05-04 12:37:58 -07:00

claude-nl-suite.yml

Sync claude-nl-suite.yml from proven main run (#759 )

2026-02-15 17:34:46 -08:00

github-repo-stats.yml

Unity MCP CI Test Improvements (#452 )

2025-12-10 14:54:55 -08:00

python-tests.yml

ci: stop firing unity-tests/python-tests twice for beta and main pushes