Website publish workflows - #5
Merged
Merged
Conversation
planger
marked this pull request as draft
July 20, 2026 17:20
planger
changed the title
planger
changed the title
Contributor
Author
|
Otterdog changes: eclipse-enclave/.eclipsefdn#3 |
xai
reviewed
Jul 21, 2026
The Eclipse Foundation provisioned a single org-level DEPLOY_TOKEN instead of separate publish and preview secrets. Grant the preview deploy job actions:read so it can fetch artifacts from the build run, and allow overriding the docs base path on a manual publish to test a deployment before eclipse.dev/enclave exists.
planger
force-pushed
the
feat/website-publish-workflows
branch
from
July 28, 2026 20:10
580d4c5 to
d44605b
Compare
planger
marked this pull request as ready for review
July 28, 2026 20:14
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds GitHub Actions workflows to publish the website (
website/) to GitHub Pagesand deploy per-PR previews, adapting the four-workflow pattern used by the Theia
website repos. The key difference from Theia: the sources live in this repo but
must publish to the separate
enclave-website/enclave-website-previewsrepos,so production uses a cross-repo branch push + legacy Pages (the same mechanism
Theia already uses for previews) rather than an in-repo
deploy-pages.What's included
website/build.sh— shared assembly: copies the static marketing site topublic/, builds the Docusaurus docs with an injectedDOCS_BASE_URL, andplaces them at
public/docs/.website-publish.yml— on push tomain(website/**), builds withDOCS_BASE_URL=/enclave/docs/and pushespublic/toenclave-website:gh-pages.website-preview-build.yml— on PR (no secrets, untrusted context), buildswith the per-PR base path and uploads
site+pr-metadataartifacts.website-preview-deploy.yml—workflow_run(trusted) pushes the preview toenclave-website-previews:previewsand comments the URL on the PR.website-preview-remove.yml— on PR close, removes the preview.All third-party actions are SHA-pinned; license headers pass; the build is verified
end-to-end locally (marketing site + docs with the correct
/enclave/docs/base URL).Draft because the workflows depend on org config that is not yet in place:
Otterdog changes (separate PR against
eclipse-enclave/.eclipsefdn):enclave-website:gh_pages_build_type: "legacy"+gh_pages_source_branch: "gh-pages"+gh_pages_source_path: "/".enclaverepo: declare secretsDEPLOY_TOKENandDEPLOY_PREVIEW_TOKEN.enclave-website.Eclipse Foundation help desk:
passstore:bots/ecd.enclave/github.com/publish-token(→
DEPLOY_TOKEN, push toenclave-website) andbots/ecd.enclave/github.com/preview-token(→
DEPLOY_PREVIEW_TOKEN, push toenclave-website-previews).Production is served at
eclipse.dev/enclavevia the EF reverse proxy (base path/enclave/); previews ateclipse-enclave.github.io/enclave-website-previews/pr-previews/pr-<N>/.