Q: How do you manage and maintain large GitHub Actions workflow files efficiently?

Transform 1000-line single YAML files into modular, maintainable building blocks:

# Matrix strategy to eliminate repeated job definitions
jobs:
  build-services:
    runs-on: ubuntu-latest
    strategy:
      matrix:
        service: [api, worker, payment, notification]
    steps:
      - uses: actions/checkout@v4
      - name: Setup environment
        uses: ./.github/actions/setup-build-env
      - name: Build service
        run: make build SERVICE=${{ matrix.service }}

• Composite Actions for Step Bundles: Group repetitive boilerplate steps (e.g. checkout, cache setup, environment configuration) into local composite actions (./.github/actions/setup-build-env).
• Reusable Workflows for Pipelines: Extract discrete lifecycle stages (build, security-scan, deploy-staging, deploy-prod) into separate reusable workflow files with explicit inputs and outputs.
• Matrix Execution: Replace copy-pasted jobs for multiple services with a dynamic matrix strategy.

Prevent YAML syntax errors, missing inputs, and unescaped script expressions before PRs merge:

# Install and run actionlint locally and in CI
npm i -g actionlint
actionlint

# Run via Docker without local installation
docker run --rm -v $(pwd):/repo --workdir /repo rhysd/actionlint:latest

• Actionlint in Pre-Commit & CI: Run actionlint to check GitHub Actions expressions (${{ }}), shell scripts inside run steps, and event webhook schemas.
• Central Orchestrator Workflow: Maintain a slim, high-level caller workflow that orchestrates dependencies between jobs using needs: [build, security-scan].
• Documentation & Granular Permissions: Enforce job-level permissions blocks and add markdown documentation in .github/workflows/README.md.