This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
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.
Add option to scripts-dev/lint.sh to only lint files changed since the last git commit #8472
Add option to scripts-dev/lint.sh to only lint files changed since the last git commit #8472
Changes from all commits
6a8bc76
4d077bb
36b3cc8
59ebd67
06226ef
16c2f54
e51baae
5fb02c9
90d195f
0056945
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
it feels to me like trying to mix
-d
and command-line parameters should be rejected: mixing the two seems confusing.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 suppose there's not much use-case for it... though I'm not sure if we explicitly need to block it either. There may a random case where someone might want to do so.
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 think you should stick to one of
[ ]
and[[ ]]
:-p(There is a difference. I can never remember what it is without looking it up.)
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.
[ ... ]
is POSIX-compliant, whereas[[ ... ]]
supports fancy bash stuff like&&
,||
,~=
etc. 1https://stackoverflow.com/questions/13542832/difference-between-single-and-double-square-brackets-in-bash
We can't make the whole script POSIX-compliant however due to our heavy use of arrays, which are undefined in POSIX.
I have changed things to be more consistent in e1abece7c though.