Skip to content

style: format with ruff; lint with ruff in CI - #12

Merged
Hj1308 merged 5 commits into
mainfrom
claude/nifty-dirac-57byzj
Oct 2, 2026
Merged

Hj1308 merged 5 commits into
mainfrom
claude/nifty-dirac-57byzj

Conversation

@Hj1308

@Hj1308 Hj1308 commented Oct 2, 2026

Copy link
Copy Markdown
Owner

Summary

  • ruff format . over the whole repo, in its own commit (8bd38ad), listed in .git-blame-ignore-revs.
  • Remaining lint findings fixed: unused imports and one unused variable, an f-string without placeholders, import a, b split, one test lambda → def, justified # noqa: E402 where import order matters (set_page_config patch in tests, BLAS thread pin in the validation harness).
  • CI lints with ruff check . and ruff format --check . (strict, no --exit-zero) instead of flake8; ruff pinned to ~=0.15.0 so a new formatter style cannot break unrelated PRs.

Verification

  • The formatting commit is AST-identical to its parent for all 19 Python files (compared with ast.dump), so it cannot change behaviour.
  • The lint-fix commit was read line by line: only import moves/removals, one unused local, one f-string, one lambda → def; no logic change. tests/data/golden_fit.json untouched.
  • ruff check . → 0 findings; ruff format --check . → 20 files formatted; 155 tests pass; validation harness runs; app smoke test loads 9 tabs.

Merge with a merge commit (not squash/rebase) so the hash in .git-blame-ignore-revs stays valid.

🤖 Generated with Claude Code

https://claude.ai/code/session_01GN1ANT89MKDjHRXcnjgSjo


Generated by Claude Code

Hj1308 and others added 5 commits October 2, 2026 20:19
CI installed the latest ruff. A new minor release can change the
formatter's style, which would make `ruff format --check` fail on
unrelated pull requests. Pin to ~=0.15.0 (the version the codebase was
formatted with) in CI and in the dev extra.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01GN1ANT89MKDjHRXcnjgSjo
@Hj1308
Hj1308 merged commit 58f48e9 into main Oct 2, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants