[Website] Add Gutenberg branch setting - #4254
Draft
fellyph wants to merge 1 commit into
Draft
Conversation
github-actions
Bot
added
[Package][@wp-playground] Website
[Type] Documentation
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
1 participant
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 changed
trunk,wp/next, andwp/latest.gutenberg-branchQuery API parameter.Why
The Query API already supports Gutenberg branch previews, but Site Settings only exposed WordPress, PHP, language, networking, and multisite controls. Users had to edit the URL manually to preview the maintained Gutenberg branches.
WordPress Core branch previews are intentionally not exposed because
wordpress-developdoes not publish matching branch artifacts; the existing WordPress Version control continues to cover release, beta, and trunk builds.User impact
Developers can choose the main Gutenberg development channels directly from Site Settings. Applying a branch creates a fresh Playground and installs the selected Gutenberg artifact.
Before and after
Before
Site Settings had no Gutenberg branch selector, so branch previews required manually editing the Query API URL.
After
Site Settings includes a Gutenberg Branch dropdown with
trunk,wp/next, andwp/latestshortcuts.Validation
npm exec nx test playground-website(370 tests)npm exec nx typecheck playground-websitenpm exec nx lint playground-websitewp/next: branch download completed, selection persisted, and Gutenberg was active.