Keep install as the default command and print how to show the help on $ bundle
#9129
+5
−7
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.
bundleasbundle installby default #9124.What was the end-user or developer problem that led to this PR?
Changing the default command, even if done in a future release is massive breaking change, and only benefits a few users which expect
$ bundleto show the help, as described in #9124.Asking everyone to configure things is very annoying and leads to "it works on my machine but not on yours".
To avoid the breakage and satisfy what both groups of users want, we print a message on
$ bundlefor how to show the help.What is your fix for the problem, implemented in this PR?
I print a message on
$ bundlefor how to show the help.Example:
The extra 2 lines seems a good compromise to handle the expectations from both groups of users.
Make sure the following tasks are checked