actions/lint
1
0
Fork 0
mirror of https://github.com/super-linter/super-linter.git synced 2024-12-26 06:32:26 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

Formatting

Browse source
This commit is contained in:
Barry 2020-06-30 15:04:46 +01:00
parent f3f8a26602
commit 9b95f4c58d
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/disabling-linters.md
View file

@ -7,7 +7,7 @@ How the changes are made differ for each linter, and also how much Super-Linter
Where a configuration file exists in your repo, it will be used in preference to the default one in the Super-Linter `TEMPLATES` directory (not in addition to it), and where one doesn't exist the `TEMPLATES` version will be used. So you should copy all configuration required from the template and not just the config you want to change.
It is possible to have custom configuration for some linters, and continue to use the default from `TEMPLATES` directory for others, so if you use Python and JavaScript and only need to tweak the Python rules, then only have a custom configuration for pylint and continue to use the default TEMPLATE from the main repo for ESLint, for example.
It is possible to have custom configuration for some linters, and continue to use the default from `TEMPLATES` directory for others, so if you use Python and JavaScript and only need to tweak the Python rules, then only have a custom configuration for pylint and continue to use the default `TEMPLATE` from the main repo for ESLint, for example.
For some linters it is also possible to override rules on a case by case level with directives in your code. Where this is possible we try to note how to do this in the specific linter sections below, but the official linter documentation will likely give more detail on this.