Output Aliases when running mage -l
#456
Open
Conversation
This file contains 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
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.
We use mage for a few projects, and noticed a minor discovery problem of the aliases we setup for our targets. While yes you can run
mage -h targetto see aliases, that's not an obvious command to know about.I have added the output of Aliases and to what targetname they point to in the
mage -loutput. That way it is more easily discoverable.If there are no aliases setup, the Aliases section won't show up. I used an actual go if block instead of as a template one as it made
errvariable management a bit simpler. But I can make adjustments if it is preferred.No new tests were added as a bunch of existing tests would fail if
Aliasesalways showed up, and the ImportLists test fails if it doesn't show up.I can add additional tests if requested though.