Update PR template to include tool renaming section#1657
Merged
tommaso-moro merged 4 commits intomainfrom Dec 23, 2025
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR enhances the pull request template by adding a new "Tool renaming" section to ensure developers don't forget to update tool aliases when renaming tools, which would otherwise break the server for users with hard references to old tool names.
- Adds a new "Tool renaming" section with checkboxes for developers to confirm whether they're renaming tools
- Includes a reference to
deprecated_tool_aliases.gowhere aliases should be added - Provides a link to documentation for detailed guidance on the tool renaming process
scutuatua-crypto
approved these changes
Dec 20, 2025
SamMorrowDrums
approved these changes
Dec 23, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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
Now that we support tool aliases for safe tool renaming, we need to ensure that aliases are introduced whenever tools are renamed. This PR updates the PR template to add a heads up to the dev opening the PR and thus ensure this process isn't neglected.
Why
If tools are renamed and their aliases are not updated, we risk breaking the server for users that have a hard reference to those tools in their server config
What changed
MCP impact
Prompts tested (tool changes only)
Security / limits
Lint & tests
./script/lint./script/testDocs