From 4175acced5f5573b0463ff0c508a20c2da3dca1b Mon Sep 17 00:00:00 2001 From: Chronos Bot Date: Fri, 4 Sep 2026 18:38:29 -0700 Subject: [PATCH] fix(ci): restore the Pages workflow a checkpoint commit deleted; validate before publishing MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit This repository has produced no CI signal since 2026-04-02 — 155 days at the time of writing — and an external health census reported it stale. The cause is not a quiet repo: `gh workflow list -R awkronos/web` returns nothing, because `.github/workflows/deploy.yml` does not exist on main. `bc104f2` "checkpoint: preserve current workspace state" (Chronos Bot, 2026-05-18) deleted it while banking a dirty working tree. Its own message says "No destructive cleanup performed"; the diff is 39 deleted lines of the repo's only workflow. That is the same shape as awkronos-compliance's a86cf04 — an automated checkpoint retiring the gate that would have reported the loss. Restored, with the deploy now gated on `npm run validate` (html-validate + stylelint). The repo has defined that script since 0.2.0 and CI never ran it, so nothing stopped a broken page from publishing. Pull requests validate and do not deploy. A daily schedule replaces the previous push-only trigger: a static spec site nobody pushes to reports nothing about whether it still builds. Verified locally: `npm ci` exit 0, `npm run validate` clean (html-validate over 7 pages, stylelint over style.css). staged-files: .github/workflows/deploy.yml --- .github/workflows/deploy.yml | 76 ++++++++++++++++++++++++++++++++++++ 1 file changed, 76 insertions(+) create mode 100644 .github/workflows/deploy.yml diff --git a/.github/workflows/deploy.yml b/.github/workflows/deploy.yml new file mode 100644 index 0000000..3abd749 --- /dev/null +++ b/.github/workflows/deploy.yml @@ -0,0 +1,76 @@ +name: Deploy to GitHub Pages + +# Restored. `bc104f2` ("checkpoint: preserve current workspace state", +# Chronos Bot, 2026-05-18) deleted this file as part of banking a dirty +# working tree, and with it went every signal from this repo: the last run +# was 2026-04-02 and an external health census read the site as 155 days +# stale. A checkpoint commit must not be able to retire a repository's only +# gate silently. +# +# Two changes on restore: +# - the deploy is now gated on `npm run validate` (html-validate + +# stylelint), which the repo has always defined and CI never ran, so a +# broken page cannot publish; +# - a daily schedule, because a static site that nobody pushes to otherwise +# reports nothing at all about whether it still builds and deploys. + +on: + push: + branches: [main] + pull_request: + branches: [main] + workflow_dispatch: + schedule: + - cron: "53 13 * * *" + +permissions: + contents: read + pages: write + id-token: write + +concurrency: + group: pages + cancel-in-progress: true + +jobs: + validate: + runs-on: ubuntu-latest + # Measured 2026-09-04: `npm ci` plus `npm run validate` completes in + # well under a minute. Ten minutes bounds a hung registry fetch. + timeout-minutes: 10 + steps: + - uses: actions/checkout@v4 + with: + persist-credentials: false + - uses: actions/setup-node@v4 + with: + node-version: 22 + cache: npm + - name: Install locked dependencies + run: npm ci + - name: Validate HTML and CSS + run: npm run validate + + deploy: + needs: validate + # A pull request validates but must never publish. + if: github.event_name != 'pull_request' + environment: + name: github-pages + url: ${{ steps.deployment.outputs.page_url }} + runs-on: ubuntu-latest + timeout-minutes: 10 + steps: + - name: Checkout + uses: actions/checkout@v4 + - name: Setup Pages + uses: actions/configure-pages@v4 + with: + enablement: true + - name: Upload artifact + uses: actions/upload-pages-artifact@v3 + with: + path: "." + - name: Deploy to GitHub Pages + id: deployment + uses: actions/deploy-pages@v4