Suggested test: copilot/mcp-issue-dependency-tools

[github-actions]

Motivation

Link to the gh-aw PR: github/gh-aw#45082 — Update GitHub MCP toolsets mapping: add issue_dependency_read and issue_dependency_write to the issues toolset.

Proposed test

• Workflow file: test-copilot-mcp-issue-dependency-tools.md
• Trigger: workflow_dispatch
• Engine: copilot
• Safe output: add-comment
• Variant: standard

Minimal test prompt sketch

Ask the agent to use the GitHub MCP server to read the dependencies of a specific issue in githubnext/gh-aw-test (using issue_dependency_read), then post an add-comment safe output with the dependency count. This exercises that issue_dependency_read is correctly registered under the issues toolset and accessible via the MCP gateway.

New fixtures or secrets needed

None — githubnext/gh-aw-test supports issue dependencies natively. A long-lived issue with known dependencies could serve as the fixture, or the test can use issue_dependency_read on any issue and assert a non-error response.

Notes

The existing test-copilot-mcp.md tests general MCP access but does not exercise issue-dependency tools specifically. test-copilot-link-sub-issue.md covers sub-issues, not dependency read/write. Adding this test closes the regression gap introduced by PR #45082.

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 · 24.4 AIC · ⌖ 5.53 AIC · ⊞ 5.6K · ◷