cli: [FIX] Fix target add command (not store targets at config file) #38
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.
This PR fixes an incorrect behavior at
target-add
command.Running
target-add
command before, new target is not add to config file:This error happen because
viper.Set()
is not invoked to save targets at config file. Is a simple commit (1 line) 1202cd4.Other points is that
target-*
commands don't have a result message to user. Example:This PR addresses it, adding messages explaining to user what is happen after running command with success state (wiki page updated).
Finally, this PR changes name of GSH CLI from
gshc
togsh
at code and wiki. Homebrew and snap installs GSH CLI asgsh
command and at this way is more clear to user this name.