Subcommand options broken in v2.6
See original GitHub issueHi! The new behavior of detecting unknown options is broken for subcommands. E.g.
$ foo bar -o=baz
The option "o" is unknown. Here's a list of all available options:
[etc]
In v2.4 (which I upgraded from) it works fine.
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (1 by maintainers)
Top Results From Across the Web
Cloudformation deploy broken #3601 - aws/aws-cli - GitHub
These seem to be command choices from aws deploy not aws ... help aws: error: argument subcommand: Invalid choice, valid choices are: push ......
Read more >git-bisect(1) - Linux manual page - man7.org
The command takes various subcommands, and different options ... that broke a feature that was known to work in version v2.6.13-rc2 of your ......
Read more >git-bisect(1) - Arch manual pages
The command takes various subcommands, and different options depending on the ... commit that broke a feature that was known to work in...
Read more >git-bisect(1) Manual Page
The command takes various subcommands, and different options depending on the subcommand: git bisect help git bisect start [<bad> [<good>.
Read more >git-bisect - Find by binary search the change that introduced a ...
The command takes various subcommands, and different options depending on the ... For example: $ git bisect skip v2.5..v2.6 This tells the bisect...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Awesome it’s already in use, thanks @ntwcklng and @leo! 🤗
@herrstucki can you checkout #87 and see if that fixes your problem?