Skip to content

W-18709355: changed messages to match new command names #972

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jun 9, 2025

Conversation

luop90
Copy link
Collaborator

@luop90 luop90 commented Jun 9, 2025

What does this PR do?

Messages printed referenced old command names, this changes them to the new names.

What issues does this PR fix or reference?

@W-18709355@

@luop90 luop90 requested a review from a team as a code owner June 9, 2025 14:53
@luop90 luop90 force-pushed the t/managed-packaging/W-18709355/command-names branch from 60db930 to 7ce6ca7 Compare June 9, 2025 14:57
@luop90 luop90 force-pushed the t/managed-packaging/W-18709355/command-names branch from 7ce6ca7 to 7c62ed2 Compare June 9, 2025 14:58
Copy link
Contributor

@jshackell-sfdc jshackell-sfdc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks for finding those pesky lingering colon-separators! LGTM

@luop90 luop90 merged commit 55e1fb6 into main Jun 9, 2025
11 checks passed
@luop90 luop90 deleted the t/managed-packaging/W-18709355/command-names branch June 9, 2025 19:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants