Feature/copilot setup steps.yml #353
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces a new GitHub Actions workflow,
copilot-setup-steps.yml, to automate the setup of a persistent Unity Editor and MCP Server environment for use with the GitHub Copilot Coding Agent. The workflow ensures that both services are started as containers, properly licensed and initialized, and persist after the workflow completes, enabling Copilot to connect to them for further automation or testing.Key changes introduced:
New CI/CD Workflow for Copilot + Unity Integration:
.github/workflows/copilot-setup-steps.yml, a comprehensive workflow that provisions and configures both a Unity Editor service container and an MCP Server service container within GitHub Actions. This setup allows for persistent, ready-to-use Unity and MCP services for Copilot integration.Service Container Management:
Automated License Activation and Project Injection:
game-ci/unity-activate@v2and securely copies the activated license and Unity project files into the Unity Editor container before startup.**Robust Initialization and Health