Document GitHub Copilot Agent network limitations in workflow#4
Document GitHub Copilot Agent network limitations in workflow#4
Conversation
|
@wwulfric Unfortunately, I hit an error while trying to use the custom Copilot setup steps configured for this repository and had to close this PR. The error I am seeing is: Once you or someone with the necessary access fixes the problem, please unassign and then reassign issue #0 to me and I'll retry. Thanks! |
|
@wwulfric Unfortunately, I hit an error while trying to use the custom Copilot setup steps configured for this repository and had to close this PR. The error I am seeing is: Once you or someone with the necessary access fixes the problem, please unassign and then reassign issue #0 to me and I'll retry. Thanks! |
|
@wwulfric Unfortunately, I hit an error while trying to use the custom Copilot setup steps configured for this repository and had to close this PR. The error I am seeing is: Once you or someone with the necessary access fixes the problem, please unassign and then reassign issue #0 to me and I'll retry. Thanks! |
Co-authored-by: wwulfric <8315997+wwulfric@users.noreply.github.com>
The
copilot-setup-steps.ymlworkflow cannot bypass GitHub's platform-level network security restrictions. Agents running in sandboxed environments encounterERR_BLOCKED_BY_CLIENTfor certain domains regardless of repository settings.Changes
martinfowler.com) that trigger platform-level blocksweb_searchContext
From PR #4, agents attempting to access
martinfowler.comfail at the platform level. Repository firewall settings and workflow configurations have no effect on these restrictions—they are enforced by GitHub's agent execution environment itself.