Appearance
CI/CD Pipelines Matrix
Overview
Every product site in the UDE ecosystem self-deploys from its own repository directly to Cloudflare Pages. There is no cross-repository trigger mechanism, no shared umbrella build, and no repository_dispatch orchestration — each repository's own push/pull_request events are sufficient to build and deploy that repository's site. Pipeline (the umbrella repo) does not build or deploy anything itself.
This replaces an earlier architecture (removed 2026-07-22) where a Pipeline-owned umbrella workflow received repository_dispatch events from child repos and orchestrated a combined build. That mechanism added a cross-repo dependency without adding real value — each repo's own CI already has everything it needs to build and deploy itself.
Pipelines Matrix
| Repository | Workflow | Deploys to | Triggers |
|---|---|---|---|
engine | publish-api-ref.yml | ude-api-ref.pages.dev | push/pull_request to main, workflow_dispatch |
design-docs | deploy.yml | ude-design-docs.pages.dev | push/pull_request to main, workflow_dispatch |
user-docs | deploy.yml | ude-user-docs.pages.dev | push/pull_request to main, workflow_dispatch |
ude_promotion | deploy.yml | ude-blog.pages.dev | push/pull_request to master, workflow_dispatch |
Pipeline | bump-submodule.yml | (none — opens a PR) | schedule (6h), workflow_dispatch |
Pipeline | integration_tests.yml | (none — regression gate) | push/pull_request to main, workflow_dispatch |
Pipeline | regression.yml | (none — trend-watch) | schedule (weekly), workflow_dispatch |
Pipeline's three workflows exist only to keep the engine/design-docs/user-docs submodule pins current and to run regression checks that need all three checked out together — they are not part of any product's deploy path.
Alerting
Every workflow above alerts on failure via a local copy of a shared Telegram/GitHub- issue notifier composite action (.github/actions/notify), duplicated into each of the five repositories rather than fetched from Pipeline at run time — this removes a cross-repo dependency that a shared, centrally-fetched action would otherwise introduce.
Related Docs
(Paths below are repository-root-relative.)
.github/AGENTS.md— per-workflow trigger and secret cataloguser-docs/docs/admin-deployment.md— deployment mechanics for a single repo's workflowuser-docs/docs/deployment/secrets.md— secrets these workflows depend on