Use official WordPress Playground PR preview action#724
Merged
Conversation
Split the build workflow into two: the build step (pull_request trigger, read-only permissions) and a separate comment workflow (workflow_run trigger, write permissions). This fixes the "Resource not accessible by integration" error for fork PRs where the GITHUB_TOKEN is read-only.
Replace the custom plugin-proxy.php approach with the official WordPress/action-wp-playground-pr-preview@v2 action, which exposes build artifacts via GitHub releases for a reliable public URL. This fixes playground previews for both fork and same-repo PRs.
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.
Summary
plugin-proxy.phpapproach with the officialWordPress/action-wp-playground-pr-preview@v2actiongenerate-playground-blueprint.jsscript and its testsContext
Follow-up to #723. The
plugin-proxy.phpendpoint relies on the GitHub APIpull_requestsfield on workflow runs, which is not populated for fork PRs. The official Playground action solves this by uploading artifacts to a GitHub release, making them publicly accessible regardless of PR origin.Test plan