mirror of
https://github.com/super-linter/super-linter.git
synced 2024-11-25 23:51:07 -05:00
7c4842d2d2
* Bump ansible-lint from 5.0.1 to 5.0.2 in /dependencies Bumps [ansible-lint](https://github.com/ansible-community/ansible-lint) from 5.0.1 to 5.0.2. - [Release notes](https://github.com/ansible-community/ansible-lint/releases) - [Commits](https://github.com/ansible-community/ansible-lint/compare/v5.0.1...v5.0.2) Signed-off-by: dependabot[bot] <support@github.com> * fix ansible * fix ansible * looking * maybe baby * adding details Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Admiral Awkbar <admiralawkbar@github.com> |
||
|---|---|---|
| .. | ||
| ansible | ||
| arm | ||
| bash | ||
| bash_exec | ||
| clojure | ||
| cloudformation | ||
| coffeescript | ||
| csharp | ||
| css | ||
| dart | ||
| dockerfile | ||
| dockerfile_hadolint | ||
| editorconfig | ||
| env | ||
| gherkin | ||
| go | ||
| groovy | ||
| html | ||
| java | ||
| javascript_es | ||
| javascript_prettier | ||
| javascript_standard | ||
| jscpd | ||
| json | ||
| jsx | ||
| kotlin | ||
| kubernetes_kubeval | ||
| latex | ||
| lua | ||
| markdown | ||
| openapi | ||
| perl | ||
| php_builtin | ||
| php_phpcs | ||
| php_phpstan | ||
| php_psalm | ||
| powershell | ||
| protobuf | ||
| python_black | ||
| python_flake8 | ||
| python_isort | ||
| python_pylint | ||
| r | ||
| raku | ||
| ruby | ||
| shell_shfmt | ||
| snakemake_lint | ||
| snakemake_snakefmt | ||
| sql | ||
| states | ||
| tekton | ||
| terraform | ||
| terraform_terrascan | ||
| terragrunt | ||
| tsx | ||
| typescript_es | ||
| typescript_standard | ||
| xml | ||
| yaml | ||
| README.md | ||
Test Cases
This folder holds test cases that are used to validate the sanity of the Super-Linter.
The format:
- Each Super-Linter language should have its own folder
- Folder(s) containing test cases for each language supported
- Passing test case(s) per language denoted in naming scheme
- FORMAT:
LANGUAGE_(TYPE)_FILE.EXTENSION - Example:
markdown_good_5.md - Note: This allows the process to understand if linting of the file should pass or fail\
- Note: (good=Standard linting should be successful bad=standard linting should fail )
- FORMAT:
- Failing test case(s) per language denoted in naming scheme
- FORMAT:
LANGUAGE_(TYPE)_FILE.EXTENSION - Example:
markdown_bad_5.md - Note: (good=Standard linting should be successful bad=standard linting should fail )
- FORMAT:
- Script to run test cases and validate the sanity of Super-Linter