Fix PR build workflow failing for fork contributors#723
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.
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
Resource not accessible by integrationerror that occurs when external contributors open PRs from forkspull_requesttrigger) keeps read-only permissions — safe for untrusted fork codeworkflow_runtrigger) runs after the build completes with write permissions to post the WordPress Playground link, running in the base repo context so it always has the necessary permissionsgenerate-playground-blueprint.jsto accept aprNumberparameter sincecontext.issue.numberis not available inworkflow_runcontextContext
Fork PRs (e.g. #720) fail because the
GITHUB_TOKENforpull_request-triggered workflows from forks is restricted to read-only, regardless of declared permissions. The two-workflow split is the GitHub-recommended pattern for this scenario.Test plan