Skip to content

ci(docs): publish from development, and retire the old hostname - #392

Merged
rubenvdlinde merged 1 commit into
developmentfrom
docs/publish-and-redirect
Aug 29, 2026
Merged

ci(docs): publish from development, and retire the old hostname#392
rubenvdlinde merged 1 commit into
developmentfrom
docs/publish-and-redirect

Conversation

@rubenvdlinde

Copy link
Copy Markdown
Contributor

Brings this app's documentation deploy up to the shape that actually publishes, and — where the app was renamed — turns the retired hostname into a redirect instead of a duplicate site.

Why the site was stale

Two independent faults, either of which alone stops the site updating:

The trigger. This workflow listened on a branch called documentation. Nobody has pushed to one since 2026-05-25, so every docs change merged to development satisfied its review and published nothing.

The secrets. A reusable workflow receives no secrets by default. With none mapped, the callee's publish step finds CF_API_TOKEN empty, skips itself on its own if: guard, and the run finishes green having changed nothing. Fixing only the trigger would have produced exactly that.

The worker name is now pinned. Deriving it is the documented way to get a green run that reaches nobody — wrangler creates the derived worker and publishes there while the custom domains keep routing to the real one.

The redirect (renamed apps only)

docs-hosts keeps the retired hostname answering, which is what stops old links breaking. On its own it also leaves two live copies of every page, so the retired app name stays as discoverable as the current one — measured across the fleet: all 13 renamed apps answered 200 on both hostnames and none redirected.

canonical-host (added in ConductionNL/.github#635) makes every non-canonical host answer 301 to the same path and query on the canonical one. Deep links and query strings survive.

Verification

The generated file is asserted before commit: triggers on development, maps CF_API_TOKEN, pins worker-name. After merge I check the live site, not the run colour — the callee's own "Verify the LIVE site serves this build" step compares only the homepage <title>, which does not change when a page is added, so it reports success either way.

Two independent faults, either of which alone stops the docs site updating.

TRIGGER. This listened on a branch called `documentation`. Nobody has pushed
to one since 2026-05-25, so every docs change merged to `development` passed
review and published nothing.

SECRETS. A reusable workflow receives no secrets by default. With none mapped,
the callee's publish step finds CF_API_TOKEN empty and skips itself on its own
guard, and the run finishes GREEN having changed nothing. Fixing only the
trigger would have produced exactly that.

The worker name is now pinned. Deriving it is the documented way to get a green
run that reaches nobody: wrangler creates the derived worker and publishes
there while the custom domains keep routing to the real one.

Where the app was renamed, `canonical-host` turns the retired hostname from a
second live copy of every page into a 301 to the same path on the current one.
@github-actions

Copy link
Copy Markdown
Contributor

Quality Report — ConductionNL/launchpad @ fe658e2

Check PHP Vue Security License Tests
lint
phpcs
phpmd
psalm
phpstan
phpmetrics
eslint
stylelint
build
check-manifest
format
check-schema-l10n
composer ✅ 104/104
npm ✅ 539/539
app:check-code ⏭️
info.xml
REUSE
PHPUnit
Newman
Playwright
Hydra gates

Quality workflow — 2026-08-29 12:43 UTC

Download the full PDF report from the workflow artifacts.

@rubenvdlinde
rubenvdlinde merged commit 3e01cb8 into development Aug 29, 2026
43 checks passed
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