GitHub Pages deploy workflow for backward-compatible dist URLs#9
Merged
Merged
Conversation
Adds a workflow that builds the monorepo and copies the JS SDK dist files to the same paths served by the old legacy Pages setup, keeping /dist/custom-widget.min.js and /examples/ URLs intact. Requires switching the repo Pages source from "legacy" to "GitHub Actions" in Settings > Pages.
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
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
packages/js/dist/files to/dist/at the site root, preserving the old URL structurepackages/js/examples/to/examples/for the same reasonAfter merging the monorepo PRs (#7 and #8), the dist files move from the repo root to
packages/js/dist/. Without this workflow, the existing GitHub Pages URLs (/dist/custom-widget.min.js,/dist/custom-widget.min.css, etc.) would break.Required manual step
The repo Pages source must be switched from "Deploy from a branch" (legacy) to "GitHub Actions" in Settings > Pages > Build and deployment > Source. The workflow handles everything else.
Test plan
https://tago-io.github.io/custom-widget/dist/custom-widget.min.jsreturns the built SDKhttps://tago-io.github.io/custom-widget/dist/custom-widget.min.cssreturns the stylesheethttps://tago-io.github.io/custom-widget/examples/basic-widget.htmlloads correctly