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
version command #11
Comments
Are we assuming that every command will be distributed via My initial thought, is we do the former for now and later we could always implement the latter, which we could use if no Thoughts? |
It's a good question, perhaps have |
If I was a command author, then I'd want to do the least amount of work as possible. |
basically I agree, I was pretty much typing as I was thinking so certainly the implementation of version would want to override the default behaviour of looking in the command's |
As noted in the first comment, we should never have the situation where a group has multiple commands with the same name if we only support |
This is a core CLI command, that will determine the version of all available commands and print them out. After some offline debate, it was decided to only support versions for commands that have a |
This should output the versions of all registered groups, e.g.
Users can then copy and paste this info into issues raised on GH. This allows a user to provide version information as easily as possible, thus increasing the likelihood that they will include this information in GH issues.
The text was updated successfully, but these errors were encountered: