In ProgressPublished: May 22, 2026

Pipeline Forge

A CLI that generates opinionated CI/CD pipeline configs from a single project manifest.

Source code

Tech stack

Node.jsTypeScript

Overview

Pipeline Forge reads one small forge.yml manifest and generates ready-to-use pipeline definitions for multiple CI providers, so you stop hand-writing near-identical YAML for every project.

Features

  • One manifest, multiple provider outputs.
  • Sensible caching and matrix defaults baked in.
  • A --check mode for verifying generated files are up to date in CI.

Roadmap

  • Core generator
  • GitHub Actions output
  • GitLab CI output
  • Plugin API for custom steps

Status

Under active development — the core generator works, provider coverage is expanding.

Knowledge base

Guides and notes related to this entry.

3 articles

  • Knowledge base

    Writing your first forge.yml

    Smallest useful manifest

    name: my-app
runtime: node
providers: [github-actions]

    Run forge generate and commit the output. Use forge --check in CI so drift fails the build.

    Next steps

    Add cache hints and a test matrix once the baseline pipeline is green. This body is stub content for the modal.

  • Knowledge base

    Caching strategies

    Defaults

    Pipeline Forge enables dependency caching when it recognizes a lockfile. Override with:

    cache:
  paths: [node_modules]
  key: lockfile-hash

    When to disable

    Turn caching off for release jobs that must fetch pristine artifacts. Stub article — replace with real guidance later.

  • Knowledge base

    Multi-provider output

    One manifest, two pipelines

    Set providers: [github-actions, gitlab-ci] and Forge emits both trees under .forge/.

    Keep provider-specific knobs in overrides: blocks so the shared base stays readable.

Tags:devtoolsci-cdautomation