Give commands friendly names #9872
Merged
+282
−216
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
davkean
force-pushed
the
dev/davkean/Commands
branch
from
22deef5 to
8ce47dd
Compare
CommandName controls the description of commands within Tools -> Customize, so they should be user friendly and based on the existing text. Also Title Cased commands to model current design guidelines.
davkean
force-pushed
the
dev/davkean/Commands
branch
from
8ce47dd to
9a3a051
Compare
drewnoakes
approved these changes
Dec 16, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
CommandName controls the description of commands within Tools -> Customize, so they should be user friendly and based on the existing text.
Also Title Cased commands to model current design guidelines.
This is to avoid this: