ci: allows checkout from forks#12256
Merged
Merged
Conversation
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
Radius functional test overviewClick here to see the test run details
Test Status⌛ Building Radius and pushing container images for functional tests... |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates Radius GitHub Actions workflows to opt into actions/checkout v7’s allow-unsafe-pr-checkout so fork-based PRs can be checked out in contexts (notably pull_request_target) where checkout is otherwise blocked.
Changes:
- Enable fork PR checkout in the cloud functional test workflow by adding
allow-unsafe-pr-checkoutto relevantactions/checkoutsteps. - Enable fork PR checkout in the shared
__changes.ymlreusable workflow checkout step.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 5 comments.
| File | Description |
|---|---|
| .github/workflows/functional-test-cloud.yaml | Adds allow-unsafe-pr-checkout to multiple checkout steps to permit fork PR checkouts in pull_request_target runs. |
| .github/workflows/__changes.yml | Adds allow-unsafe-pr-checkout to the reusable workflow’s checkout step so callers can run change-detection against fork PR refs. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #12256 +/- ##
==========================================
- Coverage 52.87% 52.86% -0.01%
==========================================
Files 751 751
Lines 48353 48353
==========================================
- Hits 25566 25564 -2
- Misses 20387 20388 +1
- Partials 2400 2401 +1 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
willdavsmith
approved these changes
Jun 25, 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
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.
Description
This pull request updates several GitHub Actions workflow files to add the
allow-unsafe-pr-checkout: trueoption to variousactions/checkoutsteps. This change ensures that workflows can check out pull request code even when GitHub's default protections would block it, which can be necessary for certain workflows or testing scenarios - PR checkout from forks.Discovered in #12070 after #12246
Error: Refusing to check out fork pull request code from a 'pull_request_target' workflow. This workflow runs with the base repository's GITHUB_TOKEN, secrets, default-branch cache scope, and runner access. Fetching and executing a fork's code in that trusted context commonly leads to "pwn request" vulnerabilities. To opt in, review the risks at https://gh.io/securely-using-pull_request_target and set 'allow-unsafe-pr-checkout: true' on the actions/checkout step.Type of change
Contributor checklist
Please verify that the PR meets the following requirements, where applicable:
eng/design-notes/in this repository, if new APIs are being introduced.