Free tool

GitHub Actions Generator

Ready-to-paste workflows: CI with a Node matrix, Vercel deploy or Docker image to GHCR with caching.

name: CI

on:
  push:
    branches: [main]
  pull_request:

jobs:
  build:
    runs-on: ubuntu-latest
    strategy:
      matrix:
        node-version: [20, 22]
    steps:
      - uses: actions/checkout@v4
      - name: Use Node.js ${{ matrix.node-version }}
        uses: actions/setup-node@v4
        with:
          node-version: ${{ matrix.node-version }}
          cache: 'npm'
      - name: Install dependencies
        run: npm ci
      - name: Lint
        run: npm run lint --if-present
      - name: Type check
        run: tsc --noEmit --if-present
      - name: Build
        run: npm run build --if-present

Built by

Miguel Ángel Colorado Marin (MACM)

Full-Stack Developer · Guadalajara, España

I develop web apps, digital tools and full projects — from design to deployment.

GitHubLinkedInBuy me a coffee
Contact me

A GitHub Actions workflow automates what you do every time you finish a change: installing dependencies, running the linter, building and deploying. Writing one by hand requires knowing the exact syntax of triggers, matrices and the official action references (actions/checkout@v4, setup-node@v4...). This generator produces three of the most-used workflows already updated to each action's latest stable version: classic CI with a Node matrix and package-manager cache, Vercel production deployment using the official CLI, and Docker image builds published to GitHub Container Registry with semi-automatic tagging and layer cache. Pick a template, package manager and triggers; copy the YAML.

Features

  • ✓Node.js CI with version matrix and cache
  • ✓Vercel deploy via vercel pull/build/deploy
  • ✓Build + push to GitHub Container Registry
  • ✓Triggers: push, PR and manual
  • ✓YAML ready for .github/workflows/

How to generate a GitHub Actions workflow?

  1. 1

    Pick the template

    Node CI, Vercel deploy or Docker image to GHCR.

  2. 2

    Configure options

    Package manager, Node versions and triggers.

  3. 3

    Create the file in your repo

    .github/workflows/ci.yml with the copied content.

  4. 4

    Check the secrets

    Vercel needs VERCEL_TOKEN; GHCR uses the automatic GITHUB_TOKEN.

Frequently asked questions

Where do workflows go?

Always under .github/workflows/ inside your repository, with a .yml extension. The filename has no functional impact but shows up in the Actions tab.

Which secret do I need to deploy to Vercel?

A personal token created at vercel.com/account/tokens, saved as VERCEL_TOKEN under Settings > Secrets and variables > Actions in your repo.

Is everything generated in my browser?

Yes, the YAML is composed locally from your options.

Related tools

Dockerfile Generator

Multi-stage, non-root, Alpine.

Nginx Config

Static, SPA or reverse proxy.

LICENSE Generator

Generate your project's LICENSE file.

.gitignore Generator

Combine technologies to generate your .gitignore.

Embed GitHub Actions Generator on your site

Add GitHub Actions Generator to any web page with a simple iframe. Free, with attribution to miguelacm.es.

<iframe
  src="https://miguelacm.es/embed/github-actions-generator"
  width="100%"
  height="700"
  frameborder="0"
  title="GitHub Actions Generator — miguelacm.es"
></iframe>
View embed in new tab →
View source on GitHub