Prevent lint-staged from linting unstaged plugin files #1266
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.
This is a follow up to #1264. I had an unstaged file in a plugin directory, and I found that lint-staged was running PHPCS on it. This is because the
composer lint:${ plugin }
command includes the plugin directory as its initial argument. This has the effect of checking all of the files in the directory tree, in addition to the staged files passed by lint-staged. To avoid this we have to run the underlyingcomposer lint
command and manually pass the--standard
arg.