Skip to content

Conversation

@IvanMurzak
Copy link
Owner

This pull request adds a new GitHub Actions workflow for Copilot setup steps. The workflow automates environment preparation for Unity development and ensures that setup steps are validated automatically when changed, while also allowing manual execution from the Actions tab.

New Copilot setup workflow for Unity environment:

  • Added .github/workflows/copilot-setup-steps.yml to define a new workflow that runs on changes and manual dispatch, specifically for Copilot setup steps.

Unity environment initialization steps:

  • Includes steps to check out code, install and initialize the Unity Editor Docker image, with logic to handle licensing issues and wait for the editor to be ready.
  • Adds installation and startup of the Unity-MCP-Server Docker image to support local development and testing.

@IvanMurzak IvanMurzak requested a review from Copilot November 13, 2025 02:51
@IvanMurzak IvanMurzak self-assigned this Nov 13, 2025
@IvanMurzak IvanMurzak added enhancement New feature or request super-feature An important feature that may improve the project drastically labels Nov 13, 2025
@IvanMurzak IvanMurzak marked this pull request as ready for review November 13, 2025 02:51
Copilot finished reviewing on behalf of IvanMurzak November 13, 2025 02:53
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This pull request introduces a GitHub Actions workflow that automates Unity development environment setup for GitHub Copilot. The workflow validates setup steps when modified and can be manually triggered, ensuring a reproducible Unity development environment with the MCP server.

Key changes:

  • New GitHub Actions workflow for automated Copilot setup validation
  • Docker-based Unity Editor and Unity-MCP-Server environment initialization
  • Unity Editor initialization monitoring with licensing issue handling

Reviewed Changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated 3 comments.

File Description
.gitignore Added .secrets to prevent accidental commit of sensitive data
.github/workflows/copilot-setup-steps.yml New workflow that sets up Unity Editor and MCP Server containers for Copilot development environment, includes initialization monitoring and error handling

Copy link
Contributor

Copilot AI commented Nov 13, 2025

@IvanMurzak I've opened a new pull request, #309, to work on those changes. Once the pull request is ready, I'll request review from you.

Copy link
Contributor

Copilot AI commented Nov 13, 2025

@IvanMurzak I've opened a new pull request, #310, to work on those changes. Once the pull request is ready, I'll request review from you.

IvanMurzak and others added 9 commits November 12, 2025 19:02
Add explicit Docker network for container-to-container communication
Co-authored-by: IvanMurzak <9135028+IvanMurzak@users.noreply.github.com>
[WIP] WIP address feedback from review on copilot action
- Remove tail fallback to ensure Unity launch failures are properly reported
- Add proper error handling when Unity fails to start with detailed logs
- Fix Unity process detection to check for both "Unity" and "unity-editor" process names
- Add container status monitoring to detect if Unity crashes
- Ensure docker run -d keeps the job non-blocking while running in background
- Add detailed error messages with full Unity logs on failure
- Start Unity Editor container without launching Unity immediately
- Create Unity license directory structure at /root/.local/share/unity3d/Unity/
- Write UNITY_LICENSE secret content to Unity_lic.ulf file
- Start Unity Editor process after license is in place
- This fixes the "No valid Unity Editor license found" error
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request super-feature An important feature that may improve the project drastically

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants