/events.json
The current production feed served from GitHub Pages at the custom domain.
Source: the ICS to JSON workflow on main.
Available resources
Source repositoryThe production JSON feed is generated from the upstream ICS source on a recurring GitHub Actions schedule. Development assets are published on demand from whichever branch you dispatch the development workflow from.
-
-
GitHub release asset
The stable release-asset URL for automated consumers that prefer GitHub downloads.
Purpose: public canonical artifact outside the Pages domain.
-
/dev/ landing page
Links to the latest development feed assets published from a manually dispatched branch run.
Purpose: validation and pre-merge testing without disturbing the production release.
-
/dev/test.json
A static realistic dummy payload for remote ingest and downstream integration testing.
Purpose: a stable non-empty staging endpoint when live data is empty or unsuitable.
How the assets are produced
Workflow runsProduction path
The ICS to JSON workflow runs on main every 30 minutes, publishes the
latest release asset, and deploys /events.json to Pages.
Development path
The ICS to JSON (Development) workflow is manual. Dispatch it from a branch to overwrite
the shared dev release and the Pages content under /dev/.
Source code
The implementation, workflow definitions, and Pages templates all live in pu-orfe/upcoming.