ci: fork PRs in regen workflow#48001
Closed
l0lawrence wants to merge 4 commits into
Closed
Conversation
The regenerate workflow resolves a microsoft/typespec PR URL to its head repo and SHA, then checks out and executes that code with a write-scoped token. When the PR originates from a fork, this runs untrusted code in a privileged job. Validate that the resolved PR head repository is microsoft/typespec and fail with an actionable error otherwise. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
l0lawrence
changed the title
l0lawrence
changed the title
l0lawrence
commented
Jul 10, 2026
l0lawrence
commented
Jul 10, 2026
l0lawrence
changed the title
l0lawrence
commented
Jul 10, 2026
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.
Problem
The
typespec-python-regenerate.ymlworkflow accepts amicrosoft/typespecpull request URL viaworkflow_dispatch. The 'Resolve TypeSpec repo/ref' step resolves that PR to its head repository + SHA (headRepositoryOwner.login/headRepository.name)Change
After resolving the PR's head repo owner/name - if it is anything else (a fork), the step fails with an actionable
::error::and exits non-zero.