Makes sure code quality stays high by checking that code is linted & formatted in CI. ### Reason Frustration — so that [things like this](https://github.com/webrecorder/browsertrix-cloud/pull/1500#issuecomment-1920087667) don't happen in the future. I tried to merge `main` into a branch to get it up to date with main, and main isn't totally formatted or linted properly, and then formatting the codebase introduced a whole bunch of unrelated changes. Running a formatter or linter shouldn't cause unrelated code changes, and `main` should always be in a correct state in terms of linting and formatting. ### Testing - [x] Test run with failing lint checks errors: https://github.com/webrecorder/browsertrix-cloud/actions/runs/7733354321/job/21085236200 - [x] Test run with failing formatting check errors: https://github.com/webrecorder/browsertrix-cloud/actions/runs/7733501666/job/21085717519 - [x] Test run with both passing lint & formatting checks passes: https://github.com/webrecorder/browsertrix-cloud/actions/runs/7733529142/job/21085796727 |
||
|---|---|---|
| .. | ||
| ansible-lint.yaml | ||
| deploy-dev.yaml | ||
| docs-publish.yaml | ||
| frontend-build-check.yaml | ||
| k3d-ci.yaml | ||
| k3d-log-ci.yaml | ||
| k3d-nightly-ci.yaml | ||
| lint.yaml | ||
| microk8s-ci.yaml | ||
| password-check.yaml | ||
| project-assign-issue.yml | ||
| publish-helm-chart.yaml | ||
| release.yaml | ||
| ui-tests-playwright.yml | ||