chore: set up github pages per pull request

[vanessatran-ddi]

Before (the change)

After (the change)

Make sure that you've checked the boxes below before you submit the PR

• I have read and followed the setup steps
• I have created necessary unit tests
• I have tested the functionality in both React and Angular.

Steps needed to test

[github-actions]

PR Preview Action v1.8.1
Preview removed because the pull request was closed.
2026-04-27 15:30 UTC

[github-actions]

Preview removed

All preview folders cleaned from gh-pages branch.

[twjeffery]

@vanessatran-ddi I tested the three previews, everything works. Nav links show correctly, subpaths work, docs search loads correctly, and both playgrounds work well

[willcodeforcoffee]

Looks good! Can't wait to try it out! 😄

[ArakTaiRoth]

@vanessatran-ddi Just a quick question? Would it be possible to modify this to only deploy the paths that need to be deployed based on changes made? If a PR is a docs only PR, then we don't need to deploy Angular and React previews for example, and vice versa. Not a blocker, just a question if we can do something quickly and easily.

[vanessatran-ddi]

@vanessatran-ddi Just a quick question? Would it be possible to modify this to only deploy the paths that need to be deployed based on changes made? If a PR is a docs only PR, then we don't need to deploy Angular and React previews for example, and vice versa. Not a blocker, just a question if we can do something quickly and easily.

@ArakTaiRoth yes technically it is possible with this add-on plugin but I don't think it is quick and easy.

1. Most of our PRs touch the svelte components, so it may affect React and Angular wrapper, so in practice, both React and Angular playgrounds would still need to rebuild on the majority of Prs.
2. To use the above plugin, I will need to modify the yaml file to split the job, add condition for each deploy step to build dynamically.
3. The current workflow is simple and predictable - every 3 Prs get 3 links, reviewers always know where to look. Conditional gate may lead to an error if the first commit doesn't touch the Svelte, but the second does and so on ...
4. For some Copilot bump dependencies, having 3 preview links are a good way to make sure nothing broke across the stack.

We can revisit if gh-pages branch becomes bigger and bigger, but for now I would rather keep this PR simple and ship it. What do you think?

[chrisolsen]

🎉 This PR is included in version 2.0.0-dev.14 🎉

The release is available on:

• npm package (@dev dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[chrisolsen]

🎉 This PR is included in version 7.0.0-dev.7 🎉

The release is available on:

• npm package (@dev dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[chrisolsen]

🎉 This PR is included in version 5.0.0-dev.7 🎉

The release is available on:

• npm package (@dev dist-tag)
• GitHub release

Your semantic-release bot 📦🚀