-
-
Notifications
You must be signed in to change notification settings - Fork 7.5k
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
Change most global flags into local ones #1652
Change most global flags into local ones #1652
Conversation
6800b37
to
597b051
Compare
For some of the commands where the cmdName is passed along in
|
This is to ensure that only the relevant command-line flags for a certain Hugo subcommand is shown to the end user, reducing clutter and improving user experience. Fixes gohugoio#1624 - CLI UX: Flags shouldn't be global
597b051
to
00d0477
Compare
The crash was introduced by commit 00d0477 in PR gohugoio#1652 where access to NoTimes was attempted even though --noTimes was not defined for the config, check and benchmark commands. Special thanks to @bep for the heads-up! See also gohugoio#1624 - CLI UX: Flags shouldn't be global
The crash was introduced by commit 00d0477 in PR gohugoio#1652 where access to NoTimes was attempted even though --noTimes was not defined for the config, check and benchmark commands. Special thanks to @bep for the heads-up! See also gohugoio#1624 - CLI UX: Flags shouldn't be global
v0.15 had it, but I removed it inadvertently for 0.16-DEV in commit 00d0477 in PR gohugoio#1652. Also add directory bash-completion for `--source` for `hugo convert`, `hugo list` and `hugo new`. See gohugoio#1624, gohugoio#1589
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
This is to ensure that only the relevant command-line flags
for a certain Hugo subcommand is shown to the end user,
reducing clutter and improving user experience.
Fixes #1624 - CLI UX: Flags shouldn't be global