RESOLVED FIXED Bug 31772
'bugzilla-tool help' should only show common commands like how 'git help' does
https://bugs.webkit.org/show_bug.cgi?id=31772
Summary 'bugzilla-tool help' should only show common commands like how 'git help' does
Eric Seidel (no email)
Reported 2009-11-21 12:48:40 PST
'bugzilla-tool help' should only show common commands like how 'git help' does We're adding more and more commands to bugzilla-tool to support the style queues and personal workflows. We don't need to show these to every user, as they would likely find them overwhelming. We need to add a flag to Command to mark it as a "common" command to be shown in the primary help. Examples of commands which we would not mark as "common": commit-queue style-queue build
Attachments
Add help command (21.18 KB, patch)
2009-11-25 13:36 PST, Eric Seidel (no email)
abarth: review+
abarth: commit-queue-
Eric Seidel (no email)
Comment 1 2009-11-25 13:36:12 PST
Created attachment 43868 [details] Add help command
Adam Barth
Comment 2 2009-11-25 13:46:12 PST
Comment on attachment 43868 [details] Add help command 4141 class Command(object): 4242 name = None 43 show_in_main_help = False We should just let this inherit instead of explicitly declaring False for a bunch of concrete commands. Otherwise looks great.
Eric Seidel (no email)
Comment 3 2009-11-25 13:49:25 PST
(In reply to comment #2) > (From update of attachment 43868 [details]) > 4141 class Command(object): > 4242 name = None > 43 show_in_main_help = False > > We should just let this inherit instead of explicitly declaring False for a > bunch of concrete commands. > > Otherwise looks great. I did that at first and then I added the = False later, as it seemed to make the Commands more self-documenting. I take it you disagree. :) (I mentioned this in the ChangeLog.)
Adam Barth
Comment 4 2009-11-25 13:59:38 PST
The other option is to remove the default. Having both the default and the explicit sets doesn't seem optimal.
Eric Seidel (no email)
Comment 5 2009-11-25 18:22:49 PST
Note You need to log in before you can comment on or make changes to this bug.