Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
This is a quick follow-up to #348, after which I was confused by this "200" because the default for the
min_cpu
parameter is50
:Cause
Defaults for these parameters were being specified in multiple places, with different values, and only one of them was being used.
Changes
can_schedule
no longer have defaults, so it is much more clear that the actual defaults come from the@click.option
attributes onscheduler
dev
parameter is now last so it can retain its default--min-gh
can be passed on the command line to specify the GitHub API rate limit threshold, with the param's previous default of 1500--max-queued
'shelp
string describes that parameter instead of some other parameter