ci(codespell): separate codespell config into standalone file #8231
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I really like `pyproject.toml` and having one place to look. But running the full backend test suite because we need to add a word to an "ignore-list" for codespell is silly. So, breaking it out into a `.codespellrc` file so that it can be updated without triggering a full CI run.
jcrist
approved these changes
Feb 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I really like
pyproject.tomland having one place to look. Butrunning the full backend test suite because we need to add a word to an
"ignore-list" for codespell is silly.
So, breaking it out into a
.codespellrcfile so that it can be updatedwithout triggering a full CI run.
I have some other ideas for reducing build times for unrelated changes but I'll open an issue to document and track those.