Closed petsam closed 6 years ago
I agree.
The nature of handling conflicting arguments within pythons argparser module makes it difficult to create a usage page which groups the arguments in a strictly logical way.
The next best solution was to label all api related arguments with API:.
I will mark this issue with an enhancement label - and at some point I might do something about it but for the time being it is not a priority.
G flag and possibly others about branch, are supposed to be used in conjuction with -a (API). In the help intro, they are not clear or mention this, neither in the Summary nor in the Sections. This led me to run a not existed flag, instead of getting the Branch name. And helped uncover another bug. Expected layout should be all API sub-flags to be under the API section of help and to be clear they need to be run together with -a I remember other programs handle it like this.