Add aliases for new actions tools #1652
Merged
+33
−1
Conversation
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
mattdholloway
previously approved these changes
Dec 19, 2025
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds deprecated tool aliases to maintain backward compatibility when migrating from individual GitHub Actions tools to new consolidated tools (actions_list, actions_get, actions_run_trigger). The aliases map old tool names to their new consolidated equivalents.
Key Changes
- Added 16 alias entries mapping old Actions tool names to three new consolidated tools
- Aliases are organized by functionality: list operations, get operations, and trigger/run operations
mattdholloway
approved these changes
Dec 19, 2025
|
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.
Summary
Why
Adding aliases because we consolidated actions tools. This allows for safely rolling out newly renamed tools without breaking server configurations that reference old tools.
What changed
MCP impact
Prompts tested (tool changes only)
Security / limits
Lint & tests
./script/lint./script/testDocs