Adds flexible caching strategies to the centralized workflows, allowing teams to optimize CI performance based on their project structure. Tested on Chief with 49% faster CI times (4m 17s → 2m 10s).

🚀 What's New

New Workflow Inputs

Two new optional inputs for frontend-pr-workflow.yml:

cache-mode: 'full' | 'node_modules-only' | 'yarn-cache-only'
  # Default: 'full' (backwards compatible)
  
disable-restore-keys: true | false
  # Default: false (backwards compatible)

Cache Modes Explained

* Workspace repos always run install to recreate symlinks

📊 Performance Results (Chief)

Before (full mode):

• Cache size: ~1.25 GB
• CI time: 4m 17s

After (node_modules-only mode):

• Cache size: ~440 MB (65% smaller)
• CI time: 2m 10s (49% faster)
• Setup time: 2m 17s → 1m 13s (47% faster)

📖 How to Use

For Workspace/Monorepo Projects

uses: Typeform/.github/.github/workflows/frontend-pr-workflow.yml@v1
with:
  app-name: 'my-monorepo'
  # cache-mode: 'full'  # Default, no need to specify

For Large Non-Workspace Projects (like Chief)

uses: Typeform/.github/.github/workflows/frontend-pr-workflow.yml@v1
with:
  app-name: 'my-app'
  cache-mode: 'node_modules-only'  # Faster restore, smaller cache

For Projects with Frequent Dependency Changes

uses: Typeform/.github/.github/workflows/frontend-pr-workflow.yml@v1
with:
  app-name: 'my-app'
  cache-mode: 'yarn-cache-only'  # Smallest cache, fast restore

🔍 How to Choose

Quick decision tree:

1. Workspace/monorepo? (has "workspaces" in package.json) → Use 'full' (default)
2. Large cache (>1GB)? → Use 'node_modules-only'
3. Frequent dependency changes? → Use 'yarn-cache-only'
4. Not sure? → Use 'full' (default)

See the Cache Strategy Guide for detailed recommendations.