Main Branch CI/CD workflow (baryhuang/mcp-remote-macos-use)

The Main Branch CI/CD workflow from baryhuang/mcp-remote-macos-use, explained and optimized by Latchkey.

What it does

This is the Main Branch CI/CD workflow from the baryhuang/mcp-remote-macos-use repository, a real project running GitHub Actions. It is shown here with attribution under its MIT license.

Below, Latchkey shows a faster, safer version produced by its optimization engine.

The workflow

name: Main Branch CI/CD

on:
  push:
    branches: [ main, master ]
    
jobs:
  build-and-test:
    runs-on: ubuntu-latest
    
    steps:
      - name: Checkout code
        uses: actions/checkout@v3
        
      - name: Set up Python
        uses: actions/setup-python@v4
        with:
          python-version: '3.11'
          cache: 'pip'
          
      - name: Install dependencies
        run: |
          python -m pip install --upgrade pip
          pip install uv
          uv pip install --system -e .
          uv pip install --system ".[dev]" pytest pytest-asyncio pyright
          
      - name: Static type checking
        run: pyright src
        continue-on-error: true
        
      - name: Run tests
        run: |
          # Explicitly set CI environment variable
          export CI=true
          # Run tests with specific flags
          python -m pytest -v -s
        continue-on-error: true
        
      - name: Build Docker image
        run: |
          docker build -t mcp-remote-macos-use:latest .
          
      # Add deployment steps here if needed 

The same workflow, on Latchkey

Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.

name: Main Branch CI/CD
 
on:
  push:
    branches: [ main, master ]
    
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  build-and-test:
    timeout-minutes: 30
    runs-on: latchkey-small
    
    steps:
      - name: Checkout code
        uses: actions/checkout@v3
        
      - name: Set up Python
        uses: actions/setup-python@v4
        with:
          python-version: '3.11'
          cache: 'pip'
          
      - name: Install dependencies
        run: |
          python -m pip install --upgrade pip
          pip install uv
          uv pip install --system -e .
          uv pip install --system ".[dev]" pytest pytest-asyncio pyright
          
      - name: Static type checking
        run: pyright src
        continue-on-error: true
        
      - name: Run tests
        run: |
          # Explicitly set CI environment variable
          export CI=true
          # Run tests with specific flags
          python -m pytest -v -s
        continue-on-error: true
        
      - name: Build Docker image
        run: |
          docker build -t mcp-remote-macos-use:latest .
          
      # Add deployment steps here if needed 

What changed

• Run on Latchkey managed runners with one line (runs-on), which apply the fixes below automatically and self-heal transient failures. This example uses latchkey-small; pick the runner size that fits the job.
• Cancel superseded runs when a branch or PR gets a newer push.
• Add a job timeout so a hung step cannot burn hours of runner time.

What Latchkey heals here

This workflow has steps that commonly fail on transient issues (network, registries, flaky browsers). On Latchkey managed runners they are detected, retried, and self-healed instead of failing your build:

• Dependency installs
• Container pulls and builds

This workflow runs 1 job per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.

Actions used in this workflow