SWI-11363 ci(playground): publish preflight playground to GitHub Pages#19
Merged
Conversation
Builds dist/playground.html on every push to main and deploys it, so sellers can demo the Migration Preflight from a URL instead of running the local build.
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
kshahbw
changed the title
joshraub-bw
approved these changes
Jul 22, 2026
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.
What
Adds a
PlaygroundGitHub Actions workflow that buildsdist/playground.htmland deploys it to GitHub Pages on every push tomain(plus manualworkflow_dispatch).Why
Sellers want to demo the Migration Preflight playground but can't run
npm run playground:buildlocally. Hosting the built file gives them a URL instead. Building in CI keeps the hosted page on the current translation engine + compatibility matrix, so it never drifts from production — same freshness guarantee as a local build, no stale committed artifact.Deploy note
Requires repo Settings → Pages → Source set to GitHub Actions (not "Deploy from a branch"). Pages URL goes live on the first push to
mainafter merge.