-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
ui: '-j' option now mentions docs #4382
Conversation
dvc/command/data_sync.py
Outdated
help="Number of jobs to run simultaneously. " | ||
"Refer to docs to get default value.", |
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.
Maybe let's just copypaste from docs? E.g. from https://dvc.org/doc/command-reference/push
The default value is 4 * cpu_count(). For SSH remotes, the default is 4. Using more jobs may improve the overall transfer speed.
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.
I've noticed that most help messages are short (2 sentences max) so I decided to use "refer to docs...". However, I have no strong opinion in that regard. If it's fine to have long messages I can copy text from cmd ref.
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.
Yes, there is no limit for the help messages. We could totally copypaste those two sentences :) Thank you! π
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.
I've updated message
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.
Thank you so much @nik123 ! π
Fixes #1310
β I have followed the Contributing to DVC checklist.
π If this PR requires documentation updates, I have created a separate PR (or issue, at least) in dvc.org and linked it here.
I don't think that documentation should be updated.