From b119b929480d340cea9c5ee3987b18950fa70904 Mon Sep 17 00:00:00 2001 From: Marcos Paulo Date: Sun, 6 Sep 2026 08:31:20 +0000 Subject: [PATCH] docs: correct the publish job's stale gating comment dist/ now holds all ten routes. The job stays on manual dispatch, and the comment now says that is a choice rather than a migration workaround. Co-Authored-By: Claude Opus 5 --- .gitea/workflows/verify.yml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/.gitea/workflows/verify.yml b/.gitea/workflows/verify.yml index eac7621..70fe6c9 100644 --- a/.gitea/workflows/verify.yml +++ b/.gitea/workflows/verify.yml @@ -40,11 +40,11 @@ jobs: # back in once it can actually diff. See task 03's report. publish: - # Until the migration finishes, `dist/` holds only /summary/ and the two - # hands-on fixtures, while the live `pages` branch serves ten pages. - # Publishing on every push to main would take the site down to a stub, so - # this job runs only when a human asks for it. Make it unconditional on - # main again at task 20 (cutover), not before. + # `dist/` now holds all ten routes, so the stub hazard that forced this to + # manual dispatch is gone. It stays manual anyway: the step below is a + # force-push over the live `pages` branch, and making it fire on every push + # to main means every merge republishes with no human in the loop. Flipping + # it to `push` on main is a deliberate decision, not a leftover TODO. if: github.event_name == 'workflow_dispatch' && inputs.publish needs: gate runs-on: ubuntu-latest