GitHub Action: frontend-build

Build the GitFit frontend from published @lax/* packages into a deployable directory. Consumed by repos that deploy the GitFit UI (e.g. Lax/workouts gh-pages).

Usage

- uses: git-fit-actions/frontend-build@v1
  with:
    config: config.json     # site config (required by git-fit-web)
    out-dir: site           # built UI output dir (default: site)

Inputs

Input	Description	Default
config	Path to the site config.json (relative to working-directory)	config.json
out-dir	Output directory for the built site (relative to working-directory)	site
working-directory	Consumer project directory containing package.json (relative to repo root)	.
npm-auth-token	PAT with read:packages for @lax GitHub Packages. Falls back to GITHUB_TOKEN (same account only)	''
stats	Path to stats.json for build-time embedding (Phase 2, reserved)	''

What it does

1. actions/setup-node@v7 (node 26, npm cache, @lax GitHub Packages registry)
2. npm ci (in working-directory)
3. npx git-fit-web build --config <config> --out <out-dir>

Requirements

• Consumer repo has a package.json depending on @lax/web-build (and the theme(s) referenced by config.json), plus a committed package-lock.json.
• To install private @lax/* packages from a different GitHub account than the publisher, pass npm-auth-token (PAT with read:packages). Within the same account, GITHUB_TOKEN + packages: read suffices.

Release

Tag v1 on mainline after changes.