Skip to content

Add codespell support with configuration and fixes#1815

Open
yarikoptic wants to merge 6 commits into
facebookincubator:mainfrom
yarikoptic:enh-codespell
Open

Add codespell support with configuration and fixes#1815
yarikoptic wants to merge 6 commits into
facebookincubator:mainfrom
yarikoptic:enh-codespell

Conversation

@yarikoptic

Copy link
Copy Markdown

Add codespell configuration and fix existing typos.

More about codespell: https://github.com/codespell-project/codespell

I personally introduced it to over a hundred of projects already mostly with a positive feedback
(see the "improveit-dashboard").

CI workflow has 'permissions' set only to 'read' so also should be safe.

Changes

Configuration & Infrastructure

  • Added [tool.codespell] section to pyproject.toml with skip patterns
  • Created GitHub Actions workflow (.github/workflows/codespell.yml) to check spelling on push to main and PRs
  • Added codespell hook to .pre-commit-config.yaml

Typo Fixes

Ambiguous typos fixed manually (2 fixes with context review):

  • lastestlatest in docs/tips.md — "Use the latest release version"
  • RUNINGRUNNING in submitit/slurm/test_slurm.py — test fixture SLURM state

Non-ambiguous typos fixed automatically via codespell -w (27 fixes in 13 files):

Common fixes include: everytimeevery time, asynchornouslyasynchronously,
submiting/submited/submisionsubmitting/submitted/submission,
runnningrunning, begginningbeginning, overidenoverridden,
instanciateinstantiate, AccesssingAccessing, informationsinformation,
uncompleteincomplete, cammandcommand, formatedformatted,
overwrittingoverwriting, whithwith, befurebefore,
genarallygenerally, detailleddetailed, concurentconcurrent,
exempleexample, catchedcaught

Historical Context

This project has had 10 prior commits fixing typos manually, demonstrating the value
of automated spell-checking.

Testing

  • Codespell passes with zero errors after all fixes

🤖 Generated with Claude Code and love to typos free code

yarikoptic and others added 6 commits April 13, 2026 07:59
- lastest -> latest (docs/tips.md:9) - "Use the latest release version"
- RUNING -> RUNNING (submitit/slurm/test_slurm.py:298) - test fixture SLURM state

Co-Authored-By: Claude Code 2.1.104 / Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Code 2.1.104 / Claude Opus 4.6 <noreply@anthropic.com>
Fixed typos:
- detailled -> detailed (README.md)
- asynchroneously -> asynchronously (docs/checkpointing.md)
- exemple -> example (docs/examples.md)
- concurent -> concurrent (docs/examples.md)
- everytime -> every time (docs/mnist.py, submitit/core/core.py)
- catched -> caught (docs/structure.md)
- submited -> submitted (docs/tips.md)
- runnning -> running (integration/preemption.py, submitit/core/plugins.py)
- whith -> with (integration/preemption.py)
- genarally -> generally (submitit/helpers.py)
- submiting -> submitting (submitit/helpers.py, submitit/core/core.py)
- begginning -> beginning (submitit/core/core.py)
- informations -> information (submitit/core/core.py)
- Accesssing -> Accessing (submitit/core/core.py)
- asynchornously -> asynchronously (submitit/core/core.py)
- submision -> submission (submitit/core/core.py)
- overiden -> overridden (submitit/core/job_environment.py)
- uncomplete -> incomplete (submitit/core/utils.py)
- instanciate -> instantiate (submitit/core/utils.py)
- cammand -> command (submitit/core/utils.py)
- formated -> formatted (submitit/slurm/slurm.py)
- befure -> before (submitit/slurm/slurm.py)
- overwritting -> overwriting (submitit/slurm/slurm.py)

Co-Authored-By: Claude Code 2.1.104 / Claude Opus 4.6 <noreply@anthropic.com>

=== Do not change lines below ===
{
 "chain": [],
 "cmd": "uvx codespell -w",
 "exit": 0,
 "extra_inputs": [],
 "inputs": [],
 "outputs": [],
 "pwd": "."
}
^^^ Do not change lines above ^^^
@meta-cla

meta-cla Bot commented Apr 13, 2026

Copy link
Copy Markdown

Hi @yarikoptic!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

5610980|RUNNING
5610980.ext+|RUNNING
5610980.0|RUNING
5610980.0|RUNNING

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

was it a typo here on purpose? I guess let's see if tests fail ;)

@meta-cla meta-cla Bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Apr 22, 2026
@meta-cla

meta-cla Bot commented Apr 22, 2026

Copy link
Copy Markdown

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant