Fix Copilot not working in forks#65492
Merged
wtgodbe merged 2 commits intoFeb 20, 2026
Merged
Conversation
Use a public runner image to allow Copilot setup steps to run in forks of the repository.
github-actions
Bot
added
the
area-infrastructure
dotnet-policy-service
Bot
added
the
community-contribution
Contributor
There was a problem hiding this comment.
Pull request overview
This PR fixes a bug where Copilot setup workflows would hang indefinitely in forked repositories due to the use of a custom runner label (8-core-ubuntu-latest) that is only available in the main dotnet organization. The fix introduces conditional logic to select the appropriate runner based on whether the workflow is running in a fork or the main repository.
Changes:
- Modified runner selection in copilot-setup-steps.yml to use conditional logic that selects
8-core-ubuntu-latestfor the main repository andubuntu-latestfor forks
martincostello
commented
Feb 20, 2026
Change condition for detecting a fork to instead just check the repo owner.
martincostello
added a commit
to martincostello/runtime
that referenced
this pull request
Mar 3, 2026
Use a public runner image to allow Copilot setup steps to run in forks of the repository. Port of dotnet/aspnetcore#65492.
akoeplinger
pushed a commit
to dotnet/runtime
that referenced
this pull request
Mar 3, 2026
Use a public runner image to allow Copilot setup steps to run in forks of the repository. Port of dotnet/aspnetcore#65492.
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.
Fix Copilot not working on forks
Use a public runner image to allow Copilot setup steps to run in forks of this repository.
Description
While looking into #65371 (comment) in my fork, I found that Agent workflows would hang indefinitely waiting for a GitHub Actions runner with the custom label to be available (because my account has no such custom runner).
Once I manually updated my main branch to use a public runner image label, things started to work.
This change should allow for .NET team members to continue to benefit from the beefier runner, while community members get something that works, even if it's slower.
If this change is taken, it should probably be applied to at least aspire, and maybe any other dotnet repos that might use the same label?