mirror of
https://github.com/super-linter/super-linter.git
synced 2024-11-24 23:21:12 -05:00
11b70102c3
- Run jscpd, gitleaks, textlint against the entire workspace instead of running them over single files, one by one. - Implement a warning function for deprecated variables. - Deprecate the VALIDATE_JSCPD_ALL_CODEBASE variable. - Remove duplicate configuration files when they are the same as the ones we provide in TEMPLATES. - Add a missing tests for ansible-lint. - Move ANSIBLE_DIRECTORY configuration when running tests in buildFileList, where similar configs are. - Simplify ansible-lint test cases to include only what's necessary, and not an entire set of roles, playbooks, and inventory. - Write instructions about major upgrades in the upgrade guide. |
||
|---|---|---|
| .. | ||
| .clj-kondo | ||
| .ansible-lint.yml | ||
| .arm-ttk.psd1 | ||
| .cfnlintrc.yml | ||
| .chktexrc | ||
| .coffee-lint.json | ||
| .ecrc | ||
| .eslintrc.yml | ||
| .flake8 | ||
| .gherkin-lintrc | ||
| .gitleaks.toml | ||
| .golangci.yml | ||
| .groovylintrc.json | ||
| .hadolint.yaml | ||
| .htmlhintrc | ||
| .isort.cfg | ||
| .jscpd.json | ||
| .lintr | ||
| .luacheckrc | ||
| .markdown-lint.yml | ||
| .mypy.ini | ||
| .openapirc.yml | ||
| .perlcriticrc | ||
| .powershell-psscriptanalyzer.psd1 | ||
| .protolintrc.yml | ||
| .python-black | ||
| .python-lint | ||
| .ruby-lint.yml | ||
| .scalafmt.conf | ||
| .shellcheckrc | ||
| .snakefmt.toml | ||
| .sql-config.json | ||
| .sqlfluff | ||
| .stylelintrc.json | ||
| .textlintrc | ||
| .tflint.hcl | ||
| .yaml-lint.yml | ||
| actionlint.yml | ||
| analysis_options.yml | ||
| php.ini | ||
| phpcs.xml | ||
| phpstan.neon | ||
| psalm.xml | ||
| README.md | ||
| sun_checks.xml | ||
| terrascan.toml | ||
TEMPLATES
The files in this folder are template rules for the linters that will run against your codebase. If you choose to copy these to your local repository in the .github/linters/ directory, they will be used at runtime. If rule files are not present locally, the templates will be used by default.
The file(s) will be parsed at runtime on the local branch to load all rules needed to run the Super-Linter GitHub Action. The GitHub Action will inform the user via the Checks API on the status and success of the process.