Github Actions

GitHub Actions Best Practices

Pipeline Architecture

Patterns

• Decompose monolithic pipelines into parallel jobs by device/locale
• Use job dependencies to create clear execution graphs
• Fail fast: put quick validation before expensive operations
• Upload artifacts on always() to enable debugging failed runs
• Set explicit timeout-minutes to prevent hung jobs
• Use matrix builds for multi-device or multi-locale testing
• Cache aggressively: Homebrew, bundler, derived data

Runner Selection

# GOOD: Apple Silicon (faster)
runs-on: macos-14
# or
runs-on: macos-15

# BAD: Intel (slower, deprecated)
runs-on: macos-12

Reliability Patterns