Problem
ruff is a declared dev dependency and is configured in pyproject.toml:
dev = ["pytest>=8.3", "pytest-asyncio>=0.24", "httpx>=0.27", "ruff>=0.7"]
[tool.ruff]
line-length = 100
.github/workflows/ci.yml never runs it. The workflow installs .[dev], runs pytest -q, seeds the demo corpus, runs the access-control eval, and uploads the report. No lint step anywhere.
So the linter is installed on every CI run and never used, and the configured line length is enforced by nothing. # noqa: ARG002 appears in app/generate.py, which shows the code was written expecting ruff to run.
Suggested approach
- Add a lint step to the
test job, after pip install -e ".[dev]" and before the tests so failures surface fast:
- name: Lint
run: ruff check .
- Add
ruff format --check . too, or explicitly decide not to and say so, so contributors know whether formatting is enforced.
- Run
ruff check . locally first and fix or explicitly configure away whatever it reports. That part is the actual work: expect a handful of findings, and please fix them rather than silencing rules wholesale.
- Add the command to
CONTRIBUTING.md so contributors can run the same check before pushing.
Done when
- CI fails on a lint violation.
- The repository is clean under its own configuration.
CONTRIBUTING.md documents the command.
Good first issue: a few lines of YAML plus whatever cleanup ruff asks for. If ruff reports something that looks like a real bug rather than style, open a separate issue for it instead of quietly fixing it in the same PR.
If you want to take this on, comment on the issue to claim it and it will be assigned. Please keep to a maximum of 2 open claims per person at a time so other contributors get a chance.
Problem
ruffis a declared dev dependency and is configured inpyproject.toml:.github/workflows/ci.ymlnever runs it. The workflow installs.[dev], runspytest -q, seeds the demo corpus, runs the access-control eval, and uploads the report. No lint step anywhere.So the linter is installed on every CI run and never used, and the configured line length is enforced by nothing.
# noqa: ARG002appears inapp/generate.py, which shows the code was written expecting ruff to run.Suggested approach
testjob, afterpip install -e ".[dev]"and before the tests so failures surface fast:ruff format --check .too, or explicitly decide not to and say so, so contributors know whether formatting is enforced.ruff check .locally first and fix or explicitly configure away whatever it reports. That part is the actual work: expect a handful of findings, and please fix them rather than silencing rules wholesale.CONTRIBUTING.mdso contributors can run the same check before pushing.Done when
CONTRIBUTING.mddocuments the command.Good first issue: a few lines of YAML plus whatever cleanup ruff asks for. If ruff reports something that looks like a real bug rather than style, open a separate issue for it instead of quietly fixing it in the same PR.
If you want to take this on, comment on the issue to claim it and it will be assigned. Please keep to a maximum of 2 open claims per person at a time so other contributors get a chance.