netcracker/ai-for-dummies
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: correct the publish job's stale gating comment

Browse Source 
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 <noreply@anthropic.com>
This commit is contained in:
Marcos Paulo
2026-09-06 08:31:20 +00:00
parent 580293867d
commit b119b92948
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.gitea/workflows/verify.yml
+5 -5
View File
@@ -40,11 +40,11 @@ jobs:
# back in once it can actually diff. See task 03's report. # back in once it can actually diff. See task 03's report.
publish: publish:
# Until the migration finishes, `dist/` holds only /summary/ and the two # `dist/` now holds all ten routes, so the stub hazard that forced this to
# hands-on fixtures, while the live `pages` branch serves ten pages. # manual dispatch is gone. It stays manual anyway: the step below is a
# Publishing on every push to main would take the site down to a stub, so # force-push over the live `pages` branch, and making it fire on every push
# this job runs only when a human asks for it. Make it unconditional on # to main means every merge republishes with no human in the loop. Flipping
# main again at task 20 (cutover), not before. # it to `push` on main is a deliberate decision, not a leftover TODO.
if: github.event_name == 'workflow_dispatch' && inputs.publish if: github.event_name == 'workflow_dispatch' && inputs.publish
needs: gate needs: gate
runs-on: ubuntu-latest runs-on: ubuntu-latest