Add local linting to development workflow #460
Labels
theme/ci
Related to build, test, and release pipeline
theme/test
Related to testing
theme/ux
Related to the user experience of the box or template
type/documentation
Improvements or additions to documentation
type/enhancement
New feature or request
Milestone
Feature description
We have opted to use github/superlinter in order to maintain better code quality in this project.
Linting needs to be available to developers before PRs are filed.
Why is it needed?
Currently, linters are used as a QA gate in Pull requests. You will not experience linter warnings/errors before being rejected on the PR. This is bad affordance and must be changed
Suggestion(s)/solution(s) [Optional]
Add
make lint
to this project. It should run the same linters as GitHub Actions in PR.Definition of done
Linting can be performed in development and will not fail in PR.
Checklist (after created issue)
The text was updated successfully, but these errors were encountered: