Reducing CI/CD Duplication with GitHub Actions Composite Actions

The problem: repeated CI steps across repositories

Many microservices share the same build steps—installing dependencies, running lint, executing tests. Copy‑pasting these blocks into each repository’s workflow leads to drift, makes updates tedious, and obscures the true CI process.

What is a composite action?

A composite action bundles multiple steps into a single, reusable unit defined in an action.yml file. It can consume inputs, run shell commands, and call other actions, all while being versioned like any other repository.

Creating a reusable composite action

# .github/actions/node-ci/action.yml
name: 'Node CI'
description: 'Install dependencies and run tests for a Node.js project'
inputs:
  node-version:
    description: 'Version of Node to use'
    required: true
    default: '18'
runs:
  using: 'composite'
  steps:
    - name: Setup Node
      uses: actions/setup-node@v4
      with:
        node-version: ${{ inputs.node-version }}
    - name: Install dependencies
      run: npm ci
    - name: Run tests
      run: npm test

Consuming the action in a workflow

# .github/workflows/ci.yml
name: CI
on: [push, pull_request]
jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: myorg/node-ci@v1
        with:
          node-version: '20'

Trade‑offs and debugging tips

• Composite actions hide the matrix; define strategy in the calling workflow if you need parallel jobs.
• Logs appear under a single step named after the action call, making it harder to see which sub‑step failed. You can add explicit name fields inside the composite to retain granularity.
• Over‑abstracting can hide details; keep the action focused on a single concern (e.g., Node setup) rather than a full pipeline.

How to verify it works

1. Push a commit to a repository that uses the composite action.
2. Go to the Actions tab, open the latest workflow run.
3. Expand the step that calls myorg/node-ci@v1 and check the logs for Setup Node, Install dependencies, and Run tests.
4. Change the node-version input and re‑run; the setup step should reflect the new version.

If the logs show the expected commands and the workflow concludes with success, the composite action is correctly versioned and reusable.

Takeaway

By extracting repeated steps into a composite action stored in its own repository, you eliminate copy‑paste, gain a single source of truth, and keep workflow files readable. Start small, version the action with tags, and gradually replace duplicated blocks across your microservices.