Skip to content

Conversation

cwillisf
Copy link
Contributor

@cwillisf cwillisf commented Sep 4, 2025

Resolves

This was built in support of #214, but I separated it out since it's useful by itself and #214 is big enough without this sort of thing in the mix.

Proposed Changes

Branches of this fork will now be published to subdirectories in GitHub Pages. To support this, the GitHub Pages publishing step has been moved from the "publish" workflow (which is associated only with real releases on npm) to the "ci" workflow. I also slightly optimized it so that all the playgrounds are published together, in one commit, instead of one each.

Reason for Changes

This makes it so we can test the spork changes before merging them into develop, and might be useful for other branches as well. Maybe it would have been nice for React 18, for example. 😅

Test Coverage

It's working for the spork branch, and should be visible for this branch as well, shortly after I press this button here...

@cwillisf cwillisf requested a review from a team as a code owner September 4, 2025 22:32
@cwillisf cwillisf added this pull request to the merge queue Sep 26, 2025
Merged via the queue into develop with commit 1faf8c1 Sep 26, 2025
16 checks passed
@cwillisf cwillisf deleted the pages-without-publish branch September 26, 2025 14:59
@github-actions github-actions bot locked and limited conversation to collaborators Sep 26, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant