mirror of
https://github.com/super-linter/super-linter.git
synced 2024-11-25 23:51:07 -05:00
00c70f4b2c
* Update snakefmt to 0.3.0 and black to 20.3 (now suppored by snakefmt). * Update pipfile for ansible 5.0 * Align pipfile python with Docker alpine image * Explicitly pin python minor version in dockerfile * Ansible updates * Add missing cryptography dependencies * Eliminate deprecated ansible syntax * Update expected output for ansible * Try to add regex to handle test run length * Yaml doc syntax fixes * Flailing attempt at tap wildcard * Catch dynamic output from ansible-lint * Update regex * Fix regex statement * Fix tap output * Update go error message (issue from master branch) * Fix regex * Ansible strikes back * Fix tap output * Fix json tap * Update r tap |
||
|---|---|---|
| .. | ||
| .clj-kondo | ||
| .ansible-lint.yml | ||
| .arm-ttk.psd1 | ||
| .cfnlintrc.yml | ||
| .chktexrc | ||
| .coffee-lint.json | ||
| .dockerfilelintrc | ||
| .ecrc | ||
| .eslintrc.yml | ||
| .flake8 | ||
| .gherkin-lintrc | ||
| .golangci.yml | ||
| .groovylintrc.json | ||
| .hadolint.yaml | ||
| .htmlhintrc | ||
| .isort.cfg | ||
| .jscpd.json | ||
| .lintr | ||
| .luacheckrc | ||
| .markdown-lint.yml | ||
| .openapirc.yml | ||
| .perlcriticrc | ||
| .powershell-psscriptanalyzer.psd1 | ||
| .protolintrc.yml | ||
| .python-black | ||
| .python-lint | ||
| .ruby-lint.yml | ||
| .snakefmt.toml | ||
| .sql-config.json | ||
| .stylelintrc.json | ||
| .tflint.hcl | ||
| .yaml-lint.yml | ||
| analysis_options.yml | ||
| phpcs.xml | ||
| phpstan.neon | ||
| psalm.xml | ||
| README.md | ||
| sun_checks.xml | ||
TEMPLATES
The files in this folder are template rules for the linters that will run against your code base. If you chose to copy these to your local repository in the directory: .github/linters they will be used at runtime. If they are not present, they will be used by default in the linter run.
The file(s) will be parsed at run time 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.