chore: apply ruff standard (line-length=88, py312, pre-commit) #9
No reviewers
Labels
No labels
domain:backend
domain:devops
domain:frontend
status:approved
status:in-progress
status:needs-fix
status:qa
type:bug
type:devops
type:feature
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
forgejo_admin/gmail-mcp!9
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "8-apply-ruff-standard-convention-python-ru"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Aligns gmail-mcp to convention-python-ruff-standard: line-length=88, target-version="py312", select=["E","F","I","W"]. Adds .pre-commit-config.yaml with ruff-format and ruff hooks.
Changes
pyproject.toml-- updated ruff config from line-length=120/py310 to line-length=88/py312, reordered select to ["E","F","I","W"].pre-commit-config.yaml-- created with ruff-pre-commit v0.15.2 (ruff-format + ruff hooks)src/**/*.py(11 files) -- reformatted to 88-char line length, broke long strings to fix 29 E501 violationstests/**/*.py(5 files) -- reformatted to 88-char line lengthTest Plan
ruff format --check .exits 0ruff check .exits 0 (0 violations)pytest tests/ -vpasses (105/105 tests)Review Checklist
ruff format --check .passesruff check .passes (0 violations).pre-commit-config.yamlhas both ruff-format and ruff hooksRelated Notes
Related
PR #9 Review
DOMAIN REVIEW
Tech stack: Python / MCP server (gmail-mcp). Convention alignment PR -- applies
convention-python-ruff-standardto this repo.pyproject.toml ruff config verified against convention template:
target-version = "py312"-- matches convention (was"py310")line-length = 88-- matches convention (was120)select = ["E", "F", "I", "W"]-- matches convention exactly (was["E", "F", "W", "I"], reordered alphabetically)extend-exclude(repo has no Alembic) -- correct.pre-commit-config.yaml verified against convention template:
ruff-pre-commitrepo withrev: v0.15.2-- matches convention templateruff-formatandruffhooks present -- matches convention requirementPython file changes (11 src + 5 test files) -- mechanical formatting only:
Annotated[...]type hints wrapped across lines -- no behavioral changeString break audit (critical for behavior correctness):
accounts.py: ValueError messages -- implicit concat, identical stringsreauth.py:"message"value uses("..." "..." "...")-- parenthesized implicit concat, identical stringfilters.py:description=(...)-- parenthesized implicit concat, identical stringmessages.py:description="..." "..."-- implicit concat, identical stringBLOCKERS
None.
NITS
8-apply-ruff-standard-convention-python-ruappears truncated (missingff-standardsuffix). Non-blocking -- the branch correctly references issue #8 and follows kebab-case convention.SOP COMPLIANCE
8-apply-ruff-standard-...references issue #8)convention-python-ruff-standard) and parent (pal-e-platform#244)PROCESS OBSERVATIONS
Clean convention alignment PR. 19 files changed, 412 additions / 120 deletions -- all mechanical. The ruff standard is now consistently applied across gmail-mcp, reducing formatting drift between repos. This brings gmail-mcp into conformance with the platform-wide
convention-python-ruff-standard.DORA impact: Reduces change failure risk (CFR) by eliminating formatting-related review friction. Pre-commit hooks will enforce going forward.
VERDICT: APPROVED