Suggested test: copilot/sandbox-exclude-env

[github-actions]

Motivation

Link to the gh-aw PR or issue: github/gh-aw#46076 — fix: exclude job-output credential env vars from agent sandbox (--exclude-env)

Proposed test

• Workflow file: test-copilot-sandbox-exclude-env.md
• Trigger: workflow_dispatch
• Engine: copilot
• Safe output: add-comment or command
• Variant: standard (sandbox enabled)

Minimal test prompt sketch

Create a workflow that sets a job-output env var containing a credential-like value, then invokes the agent. The agent attempts to read the excluded env var inside the sandbox and reports what it sees (or cannot see). The harness asserts the agent run succeeds without leaking the credential into the sandbox environment, confirming the --exclude-env fix works end-to-end.

New fixtures or secrets needed

A dummy (non-secret) env var name to act as the credential placeholder — no real secrets needed.

Notes

Existing test-copilot-network-isolation.md covers firewall/network isolation but not env-var exclusion. This is a regression test for the sandbox leak fixed in PR #46076.

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• awmgmcpg

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "awmgmcpg"

See Network Configuration for more information.

Generated by 🔍 Suggest New E2E Tests · 26.7 AIC · ⌖ 5.61 AIC · ⊞ 5.6K · ◷