chore: enforce frontend and backend linting - #11
Merged
Conversation
Pull requests could previously build successfully without checking frontend or backend source quality, allowing avoidable defects to reach main. Add Oxlint for the React frontend and Ruff plus Bandit for Python. Run all three in a dedicated pull-request workflow, clean up existing findings, and document the same mandatory checks for contributors and coding agents.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Why
Pull requests could build successfully without checking frontend or backend
source quality, so avoidable correctness and security findings could reach
main. Contributors and coding agents also had no shared linting contract tocatch those failures before CI.
What
Add Oxlint for the React frontend and Ruff plus Bandit for Python, with pinned
tooling and repository-owned rule configuration. A dedicated pull-request
workflow installs and enforces both suites, while the agent guide and local
development documentation use the same commands. Existing findings are fixed
or narrowly documented where Bandit reports an intentional safe pattern, and
the frontend build moves to Node.js 22 to satisfy current Oxlint requirements.