Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Repository Structure

Astrid Avalin Soerensen edited this pageMay 9, 2025 ·3 revisions

🗂️ Repository Structure

🧠 Main Workflows

FilePurpose
ci-cd-dispatcher.ymlEntry-point dispatcher: validates inputs, prepares metadata, and triggers CI/CD
ci-cd-deployer.ymlDeploy from a GitHub release to selected targets
ci-cd-pipeline.ymlFull pipeline: test, build, release, deploy & notify

🤩 Modular Reusable Templates

Each stage is its own reusableworkflow_call:
FilePurpose
step-0-analyze.ymlRuns static analysis usingdotnet format
step-1-test.ymlDetects and runs Unity tests
step-2-build.ymlBuilds for up to multiple targets
step-3-release.ymlPublishes GitHub releases
step-4-deploy.ymlDeploys to platforms like itch.io, S3, Steam, etc.
step-5-notify.ymlSends Discord, Slack, and Teams notifications
unity-tests-detection.ymlDetects if EditMode / PlayMode tests exist
unity-tests-runner.ymlRuns Unity tests for specified mode
unity-license-uploader.ymlUploads Unity.ulf license

Let’s build better Unity pipelines together! 🚀
Need help? Join theDiscussions or open anIssue.

Clone this wiki locally

[8]ページ先頭

©2009-2025 Movatter.jp