[mcp-tools] Update GitHub MCP toolsets mapping: add issue dependency tools

[github-actions]

Summary

Adds issue_dependency_read and issue_dependency_write to the GitHub MCP toolsets mapping, registering both tools under the issues toolset.

Changes

pkg/workflow/data/github_tool_to_toolset.json

• Added "issue_dependency_read": "issues" and "issue_dependency_write": "issues" entries.

pkg/workflow/data/github_toolsets_permissions.json

• Extended the issues toolset tools array with issue_dependency_read and issue_dependency_write (inserted alphabetically).
• No permission scope changes; read/write permissions remain ["issues"].

pkg/workflow/github_tool_to_toolset_test.go

• Added 4 test cases to TestValidateGitHubToolsAgainstToolsets:
  • issue_dependency_read and issue_dependency_write resolve correctly when the issues toolset is enabled.
  • Both tools produce the expected validation error when only the repos toolset is enabled.
• Added both tools to the consistency map in TestGitHubToolToToolsetMap_ConsistencyWithDocumentation.

Motivation

The GitHub MCP server introduced issue_dependency_read and issue_dependency_write tools for managing issue dependencies. Without this mapping, workflows using those tools would fail toolset validation.

Test coverage

All new mappings are covered by positive and negative test cases in the existing github_tool_to_toolset_test.go test suite.

Generated by PR Description Updater for #45082 · 20.9 AIC · ⌖ 6.86 AIC · ⊞ 4.7K · ◷

[github-actions]

Hey @github-actions 👋 — thanks for this automated update to the MCP toolsets mapping, adding issue_dependency_read and issue_dependency_write to the issues toolset! The change is well-scoped and the PR description is thorough, including a clear rationale for what was intentionally omitted.

One small thing that would strengthen this:

• Add or update a test — pkg/workflow/data/github_toolsets_permissions.json is a data file but if there are snapshot or validation tests covering the toolset inventory, they should be updated to include the two new tool entries.

If you'd like a hand, you can assign this prompt to your coding agent:

Check whether there are any tests or validation fixtures that cover pkg/workflow/data/github_toolsets_permissions.json.
If so, update them to include the two new entries added in this PR:
- issue_dependency_read (read, issues toolset)
- issue_dependency_write (write, issues toolset)
Ensure all existing tests still pass after the update.

Generated by ✅ Contribution Check · 128.4 AIC · ⌖ 10.6 AIC · ⊞ 6.2K · ◷

[gh-aw-bot]

@copilot please run the pr-finisher skill, address any unresolved review feedback, and rerun checks once the branch is up to date.

Run: https://github.com/github/gh-aw/actions/runs/29196572530

Generated by 👨‍🍳 PR Sous Chef · 8.11 AIC · ⌖ 5.41 AIC · ⊞ 4.2K · ◷
_{Comment /souschef to run again}

[Copilot]

@copilot please run the pr-finisher skill, address any unresolved review feedback, and rerun checks once the branch is up to date.

Run: https://github.com/github/gh-aw/actions/runs/29196572530...

Done. The contribution-check feedback pointed to missing test coverage and a missing entry in github_tool_to_toolset.json (the file used for runtime tool validation).

Changes in commit fix: add issue_dependency tools to github_tool_to_toolset.json and test coverage:

• Added issue_dependency_read and issue_dependency_write to pkg/workflow/data/github_tool_to_toolset.json (the original PR only updated github_toolsets_permissions.json)
• Added 4 new test cases to TestValidateGitHubToolsAgainstToolsets covering both tools
• Added both tools to TestGitHubToolToToolsetMap_ConsistencyWithDocumentation

Local validation passes: make fmt, make lint, make test-unit, make agent-report-progress all green.

[gh-aw-bot]

@copilot please run the pr-finisher skill, address any unresolved review feedback, and rerun checks once the branch is up to date.

Run: https://github.com/github/gh-aw/actions/runs/29200137487

Generated by 👨‍🍳 PR Sous Chef · 8.57 AIC · ⌖ 7.74 AIC · ⊞ 7.5K · ◷
_{Comment /souschef to run again}

[Copilot]

@copilot please run the pr-finisher skill, address any unresolved review feedback, and rerun checks once the branch is up to date.

Run: https://github.com/github/gh-aw/actions/runs/29200137487...

No new issues found. The PR is already in merge-ready state from the previous pass (commits 2c888d1 and f0ab87d). The Sous Chef run that triggered this had no new findings. Local tests still green.

[gh-aw-bot]

\n@copilot please run the pr-finisher skill, address unresolved review comments, and rerun checks once the branch is up to date.

Generated by 👨‍🍳 PR Sous Chef · 5.74 AIC · ⌖ 6.61 AIC · ⊞ 7.5K · ◷
_{Comment /souschef to run again}

[gh-aw-bot]

pr-sous-chef
@copilot please run the pr-finisher skill, address any unresolved review feedback, and rerun checks once the branch is up to date.

Run: https://github.com/github/gh-aw/actions/runs/29214279165

Generated by 👨‍🍳 PR Sous Chef · 13.2 AIC · ⌖ 8.72 AIC · ⊞ 7.5K · ◷
_{Comment /souschef to run again}

[Copilot]

\n@copilot please run the pr-finisher skill, address unresolved review comments, and rerun checks once the branch is up to date.

...

Local validation passes (make fmt, make lint, make test-unit, make agent-report-progress). No unresolved review threads — the contribution-check feedback was already addressed in commit f0ab87d. PR is merge-ready pending a human CI re-trigger.

pr-sous-chef
@copilot please run the pr-finisher skill, address any unresolved review feedback, and rerun checks once the branch is up to date.
...

Local validation passes (make fmt, make lint, make test-unit, make agent-report-progress). No unresolved review threads — the contribution-check feedback was already addressed in commit f0ab87d. PR is merge-ready pending a human CI re-trigger.

[github-actions]

🎉 This pull request is included in a new release.

Release: v0.82.9