Nagato AI CI/CD workflow (kenshiro-o/nagato-ai)

The Nagato AI CI/CD workflow from kenshiro-o/nagato-ai, explained and optimized by Latchkey.

What it does

This is the Nagato AI CI/CD workflow from the kenshiro-o/nagato-ai 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: Nagato AI CI/CD
on:
  push:
    branches:
      - main
    tags:
      - v[0-9]+\.[0-9]+\.[0-9]+
  pull_request:
    branches:
      - main

permissions:
  contents: read
  id-token: write
  checks: write

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Install uv
        uses: astral-sh/setup-uv@v5
        with:
          python-version: '3.12'

      - name: Install ffmpeg
        run: sudo apt-get update && sudo apt-get install -y ffmpeg

      # Install dependencies
      - run: make install-ci

      # Run linter - and fail if score if below a certain threshold
      # TODO: Uncomment when we have a linter threshold
      # - run: make lint-ci

      # Run tests
      - run: make test-debug

The same workflow, on Latchkey

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

name: Nagato AI CI/CD
on:
  push:
    branches:
      - main
    tags:
      - v[0-9]+\.[0-9]+\.[0-9]+
  pull_request:
    branches:
      - main
 
permissions:
  contents: read
  id-token: write
  checks: write
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  build:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
      - uses: actions/checkout@v4
 
      - name: Install uv
        uses: astral-sh/setup-uv@v5
        with:
          python-version: '3.12'
 
      - name: Install ffmpeg
        run: sudo apt-get update && sudo apt-get install -y ffmpeg
 
      # Install dependencies
      - run: make install-ci
 
      # Run linter - and fail if score if below a certain threshold
      # TODO: Uncomment when we have a linter threshold
      # - run: make lint-ci
 
      # Run tests
      - run: make test-debug
 

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.

1 third-party action is referenced by a movable tag. Pin it to the commit SHA (Latchkey resolves and applies this automatically) so a repointed tag cannot change what runs.

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

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