ci: Add code quality workflow and linter configurations #25
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.
Pull Request
Description
This change introduces a new code quality workflow and configuration files for various linters. The key additions include:
A new GitHub Actions workflow file (
code-quality.yml
) that runs the Super-Linter on push to main and pull requests.Configuration files for different linters:
.ecrc
for EditorConfig linter.eslintrc.yml
for ESLint, including specific configurations for JSON and JSON5 files.jscpd.json
for copy-paste detection.markdown-lint.yml
for Markdown linting.yaml-lint.yml
for YAML lintingThe Super-Linter is configured to validate all codebase against the main branch, using custom rules defined in the
.github/super-linter-configurations
directory.Python-specific linters (Black, Flake8, isort, MyPy, Pylint, Ruff, and Pyink) are disabled in the workflow.
This change aims to improve code quality and consistency across the project by implementing automated linting checks.
fixes #9