fix: Restrict CSpell to just markdown files at the configuration level#518
fix: Restrict CSpell to just markdown files at the configuration level#518
Conversation
|
Where was the file scoping before? |
|
The GitHub Action Threw this at the wall to see if the project-level configuration would override it; seems to have failed. I'll have to look into CI more closely to see where/how configuration needs to be updated. (CI would probably still fail on the codecov problem we fixed in prod anyway) |
|
The reason why I ask is that Shorebird CI is designed to be zero-config. So if there are other config spots that we aren't reading for CSpell and should be, that is a problem. But main.yaml is not a CSpell config spot, rather a GitHub Actions config so it seems fine for us to ignore. Thanks! |
Not sure if this will work as intended.
This fix moves the file scoping into
.cspell.yamlitself, the project-level config, so that no matter which runner invokes CSpell or how it's configured, only markdown files get checked. The Shorebird CI pulls in a separate.cspell.yamlworkflow that runs CSpell with no file filter, so it checked all files. This should allow us to only be spell checking markdown as intended and not be failing CI (DEV) because of misspellings in, for example,package.json.