deploy.yml

# Build the static site and publish it to GitHub Pages.
#
# ONE-TIME SETUP REQUIRED. This repository currently serves master's root
# directory directly. Before this workflow can deploy anything, change
# Settings -> Pages -> Build and deployment -> Source to "GitHub Actions".
# Until that switch is flipped, this workflow will build successfully and the
# deploy step will fail.
#
# public/CNAME carries the www.cmdm.tw custom domain into dist/, so the domain
# survives the switch.

name: Deploy site

on:
  push:
    branches: [master]
  workflow_dispatch:

permissions:
  contents: read
  pages: write
  id-token: write

# Let a queued deploy wait for the running one rather than cancelling it: a
# half-finished Pages deployment is worse than a slightly stale one.
concurrency:
  group: pages
  cancel-in-progress: false

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - uses: actions/setup-node@v4
        with:
          node-version: 22
          cache: npm

      - run: npm ci

      # The privacy tripwire runs before anything is published. data/members.yml
      # is derived from a private repository, so a leak must block the deploy,
      # not be discovered on the live site.
      #
      # The runner's Node is newer than the one this is developed on, and the
      # first deploy failed here for that reason alone: `npm test` was
      # `node --test tests/`, which Node 20 accepts as a directory to walk and
      # Node 22 and 24 read as a module path. It passes explicit files now, which
      # every version accepts. Worth running the tests on the CI Node before
      # pushing rather than finding out here.
      - name: Run tests
        run: npm test

      - name: Build
        run: npm run build

      - uses: actions/configure-pages@v5
      - uses: actions/upload-pages-artifact@v3
        with:
          path: dist

  deploy:
    needs: build
    runs-on: ubuntu-latest
    environment:
      name: github-pages
      url: ${{ steps.deployment.outputs.page_url }}
    steps:
      - id: deployment
        uses: actions/deploy-pages@v4