Repository files navigation

Robust GitHub Actions workflows for Unity projects. Automates testing, multi-platform builds, and GitHub Releases with modular, reusable design.

See a live WebGL build deployed using this CI/CD pipeline:

➡️Play the Demo

Deployed via GitHub Pages using thegh-pages deploy target.

1️⃣ Ensure your Unity project is in a GitHub repository
2️⃣ Copy the required GitHub Actions workflows from theCICD_Workflows folder
3️⃣ Add them to your repository at path:.github → workflows(create folders if missing)
4️⃣ Configure therequired secrets in your repository
5️⃣ Read and optionally setuprepository variables, they're important to understand the inputs for the workflow dispatch
6️⃣ Try dispatching theci-cd-dispatcher.yml workflow or push a Git tag usingSemVer to see the pipeline in action!

⚠️ Currently tested deploy targets:gh-pages (WebGL only),itch.io. Others are implemented but not yet fully verified. Contributions welcome!

For full setup instructions, deployment target guides, and advanced configuration tips, see the ➡️Wiki

While the pipeline is production-ready and modular, some deploy integrations are still marked asexperimental:

• 🚧Deploy targets like Steam, TestFlight, App Center
  These are implemented but have not yet been fully validated in live release pipelines.

• 🔗External platforms may require manual setup
  Some targets (like itch.io, Firebase, S3) require correctly configured secrets and accounts - be sure to test deploy flows in a safe sandbox environment before pushing to production.

• 🧪Unity version compatibility
  Currently optimized for Unity 2022.3+, tested with Unity 6 too, but older versions may work as well.

Contributions and testing feedback are welcome!
If you successfully validate additional targets or add new ones, please consider opening a PR to improve support for the community.

Crafted with ❤️ byAvalin
Special thanks toRedGlow for contributions 💡
Powered by GitHub Actions + Unity + Tears.(PRs welcome!)