Skip to content

chore(site): retire GitHub Pages — ultralog.co builds from releases - #106

Merged
SomethingNew71 merged 2 commits into
mainfrom
chore/retire-github-pages
Oct 25, 2026
Merged

SomethingNew71 merged 2 commits into
mainfrom
chore/retire-github-pages

Conversation

@SomethingNew71

Copy link
Copy Markdown
Collaborator

ultralog.co now runs from ClassicMiniDIY/ultralog-site on a Cloudflare Worker (live since 2026-10-25). This PR retires the GitHub Pages copy and wires releases to rebuild the new site.

Changes

  • Delete the Pages files: docs/index.html, docs/CNAME, docs/robots.txt, docs/sitemap.xml, docs/.nojekyll. docs/FORMAT_SPECIFICATIONS.md and docs/plans/ stay.
  • scripts/bump-version.sh: drop the docs/index.html version-badge step. The site reads the version from the GitHub release.
  • release.yml: after the release and its assets exist, send repository_dispatch (app-release) to ultralog-site. A release: published workflow cannot do this, because releases created with GITHUB_TOKEN start no other workflow. The step has continue-on-error, and the site's daily build is the backstop.
  • New site-dispatch.yml: the same dispatch when a release is edited, published or deleted by hand (for example gh release edit for the notes). The job is skipped outside this repo.
  • CLAUDE.md: the website contract.

The secret SITE_DISPATCH_TOKEN (a fine-grained PAT with Contents write on ultralog-site only) is already set on this repo.

Merge order (do not merge first)

GitHub Pages is still enabled (main /docs), and the ultralog.co domain is not verified with GitHub. Some resolvers still use the old Route 53 delegation, which points at GitHub's Pages IPs. If this PR merged while Pages is on, those users would get a 404, and another GitHub account could claim ultralog.co for its own Pages site and serve it to them. So:

  1. In the Route 53 hosted zone, point ultralog.co A/AAAA at Cloudflare, or delete the zone.
  2. Turn off Pages: gh api -X DELETE repos/ClassicMiniDIY/UltraLog/pages.
  3. Merge this PR.

Conflict to expect

release/3.0.0 edits docs/index.html and docs/sitemap.xml, which this PR deletes. When that branch merges, keep the deletion. The 3.0 What's New copy already lives in ultralog-site (app/data/content.ts).

Review

Opus Code Reviewer pass on 9ae53aa:

  • Workflow placement, token handling and the bump-version.sh change are correct.
  • A fine-grained PAT with Contents write is the documented permission for POST /dispatches.
  • Nothing else in the repo depends on the deleted files.
  • Its fork-run note is fixed in 0fc55dc, and its ordering blocker is the "Merge order" section above.

The site now lives in ClassicMiniDIY/ultralog-site on Cloudflare. Remove the
Pages files and the docs/index.html version bump. release.yml dispatches a
site rebuild after a release's assets upload, and site-dispatch.yml does the
same for releases edited, published or deleted by hand.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant