-
Notifications
You must be signed in to change notification settings - Fork 2.1k
use 'config' over 'configuration file' #785
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
use 'config' over 'configuration file' #785
Conversation
Codecov Report
@@ Coverage Diff @@
## master #785 +/- ##
======================================
Coverage 50.9% 50.9%
======================================
Files 237 237
Lines 15338 15338
======================================
Hits 7808 7808
Misses 7028 7028
Partials 502 502 |
dnephin
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SGTM
one nit on wording for create
cli/command/config/create.go
Outdated
| cmd := &cobra.Command{ | ||
| Use: "create [OPTIONS] CONFIG file|-", | ||
| Short: "Create a configuration file from a file or STDIN as content", | ||
| Short: "Create config using a file or STDIN as content", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about:
"Create a config from a file or STDIN"
dnephin
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
vdemeester
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 😛
cc @thaJeztah
thaJeztah
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM "configuration file" was in an attempt to make the purpose more clear, but I agree it wasn't consistent, and not really adding much
@friism can you squash your commits? Then we can merge 👍
Signed-off-by: Michael Friis <friism@gmail.com>
fc8eb74 to
99e3b4c
Compare
|
squashed, thanks guys |
…nsistent use 'config' over 'configuration file' Upstream-commit: a60bdf3 Component: cli
- What I did
The help text for
configcommands is not consistent about whether the object being modified is called a "config" or a "configuration file". I changed it to be "config" for all commands since that's shorter.Previously:
- How to verify it
docker config --help- Description for the changelog
Descriptions for config commands now use the same name when describing configs.