🪲 [Fix]: Add .codespellrc to skip linter config directory#9
Conversation
No Significant Changes DetectedThis PR does not contain changes to files that would trigger a new release:
Build, test, and publish stages will be skipped for this PR. If you believe this is incorrect, please verify that your changes are in the correct locations. |
There was a problem hiding this comment.
Pull request overview
Adds a codespell configuration to prevent Super-Linter’s SPELL_CODESPELL check from flagging intentional “misspellings” inside linter configuration files under .github/linters.
Changes:
- Added
.github/linters/.codespellrcwith a skip rule for.github/linters. - Added an ignore-words entry for
afterall.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| @@ -0,0 +1,3 @@ | |||
| [codespell] | |||
| skip = ./.github/linters | |||
There was a problem hiding this comment.
codespell path matching can vary between emitting paths like .github/linters/... vs ./.github/linters/.... To make the skip rule more robust, consider dropping the leading ./ (or include both patterns) so the directory is reliably skipped regardless of how paths are reported.
| skip = ./.github/linters | |
| skip = .github/linters |
Super-linter summary
All files and directories linted successfully For more information, see the GitHub Actions workflow run Powered by Super-linter |
Context
The super-linter
SPELL_CODESPELLcheck flags intentional misspellings in.github/linters/.textlintrc(e.g.environemnt,pacakge). These strings exist as linter configuration patterns and are not actual typos.The GitHub, GoogleFonts, and NerdFonts repos already solved this by adding a
.codespellrcfile.Changes
.github/linters/.codespellrcthat tells codespell to skip the.github/lintersdirectory and ignore the wordafterall