18 Free GitHub Actions and CI Recipes for Unity and Godot Builds (2026)

Core reference for workflow syntax, runners, contexts, matrices, and reusable workflow patterns.
Start here: align your team on one canonical CI vocabulary.

Detailed YAML keys and behavior rules for triggers, jobs, steps, conditions, and concurrency controls.
Use for: debugging subtle workflow ordering and environment issues.

Popular open-source Unity build action for Linux/macOS/Windows runners with license activation options.
Best for: repeatable branch builds—pair with cache-bust before player packaging, not compile-only green.

CI-friendly Unity test execution for edit mode and play mode validations with report outputs.
Use for: gating merges before expensive full-platform builds.

License activation/deactivation recipe for headless Unity CI sessions on ephemeral runners.
Critical for: reducing random pipeline failures tied to activation state.

Command-line export reference for scripted desktop/web build outputs and preset-driven CI usage.
Best for: deterministic Godot exports without editor UI steps (lane unchanged by Unity false-green appendix).

Prebuilt Docker images for Godot exports including templates and toolchain utilities.
Use for: faster setup when standardizing runner environments.

Built-in dependency and build cache action for Unity Library/ and Godot import caches.
Pro tip: include engine version, platform, and Addressables catalog hash; run one weekly no-cache job on main—detail stack: false-green debug tools.

Official content-state contract—hash AddressablesContentState.bin (or catalog JSON) into cache keys and addressables_ci_cache_receipt_v1.json.
Fail when: group rename without key bust (CI green, player InvalidKeyException).

Artifact upload action for sharing build outputs, logs, and test reports between jobs and teams.
Best for: release candidate review and reproducible QA handoffs.

Artifact retrieval action for multi-stage pipelines where deploy jobs consume build outputs from earlier jobs.
Use for: clean separation of build, test, and publish steps.

.NET SDK setup action for Unity tooling scripts, analyzers, or supporting backend utilities.
Useful for: mixed game + tooling repos with shared C# checks.

Node.js setup action for web build helpers, changelog scripts, and release automation tasks.
Use for: packaging metadata or storefront automation around game builds.

Parallel build matrix guide for OS/platform combos and versioned export targets.
Best for: validating Windows/macOS/Linux outputs in one workflow.

Concurrency and cancel-in-progress docs to avoid duplicate long-running builds—and poisoned Library/ when cancel mid-Addressables.
Critical for: never share one concurrency group between lint and player packaging jobs.

Secure secret and environment variable management for license keys, API tokens, and deploy credentials.
Use for: safe automation without leaking production keys in logs.

Dedicated false-green stack—catalog hash, weekly no-cache, jq receipt gates, Guide #24, Lesson 261.
Contrast: this list = build graph; that list = cache-poison recovery.

Player-side recovery—when CI was green but the installed build throws InvalidKeyException after group moves.
Pair with: content-state hash row + false-green list for preventive policy.