Skip to content

docs: CONTRIBUTING.md references yapf/Google style guide, but pre-commit actually runs black + flake8 - #1504

Open
PARINAYKAPOOR wants to merge 1 commit into
ModelTC:mainfrom
PARINAYKAPOOR:fix/contributing-docs-style-tools
Open

docs: CONTRIBUTING.md references yapf/Google style guide, but pre-commit actually runs black + flake8#1504
PARINAYKAPOOR wants to merge 1 commit into
ModelTC:mainfrom
PARINAYKAPOOR:fix/contributing-docs-style-tools

Conversation

@PARINAYKAPOOR

@PARINAYKAPOOR PARINAYKAPOOR commented Aug 25, 2026

Copy link
Copy Markdown

What's wrong

CONTRIBUTING.md tells contributors to follow the Google Python style guide and format code with yapf. But .pre-commit-config.yaml only configures black (line-length 120) and flake8 — there's no yapf config anywhere else in the repo. This is stale documentation, presumably left over from before the project switched formatters.

A new contributor following CONTRIBUTING.md as written would install/run the wrong tool (yapf) and could still fail the actual pre-commit check, which runs black.

What this changes

Updates the "Coding Style Guide" section of CONTRIBUTING.md to name the tools that are actually enforced (black, flake8), matching .pre-commit-config.yaml. No functional/code changes.

Test plan

  • Compared CONTRIBUTING.md against .pre-commit-config.yaml; confirmed black + flake8 are the only formatters configured repo-wide.
  • Searched the repo for any yapf config (.style.yapf, etc.) — none found outside the doc text being changed.

…e8, not yapf)

pre-commit is configured to run black (line-length 120) and flake8
(see .pre-commit-config.yaml), but CONTRIBUTING.md still told new
contributors to follow the Google Python style guide and use yapf.
There is no yapf config anywhere else in the repo, so this was just
stale documentation left over from before the project switched
formatters. Updated the doc to match what pre-commit actually enforces,
so first-time contributors format their code correctly on the first try.
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.

1 participant