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.
The name of the
--maxdepth
option is inconsistent with all of the other--max-*
options, and aside from being aesthetically displeasing it affects the ordering in the help output and completion results. I assume the wordingmaxdepth
comes fromfind
, and that makes sense on its own i guess, but... it just feels out of place to me here.This PR changes the canonical name of the option to
max-depth
, leavingmaxdepth
as a hidden alias for backwards compatibility.(I realise this is petty; feel free to just close if i'm being too ridiculous...)