You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
incremental_files_only appears to be ignored #2325
While trying to provide a small cspell.json that could reproduce this I found that it was specifically caused by a files entry in the configuration which looked like the following:
Removing that files entry would cause the GitHub action to work as expected. Locally this files configuration already works as expected.
My hypothesis is that this could be a difference between how the GitHub action interprets this vs how CSpell itself does so. Or it's a platform difference (Mac locally; Linux in the CI).
Re-reading the documentation, I suspect that our configuration might be invalid (it's not actually a glob?) but it's not exactly clear to me whether that's true or why it would then still work on our local development machines.
Activity
Jason3S commentedon May 28, 2025
@tpeterson-metropolis,
Thank you. I'll see if I can reproduce it.
Jason3S commentedon May 28, 2025
@tpeterson-metropolis,
I'm not able to reproduce the issue you are seeing.
It causes an error for me: streetsidesoftware/cspell-action-example#2
Do you have an example repo that shows the issue?
Kingdutch commentedon Aug 6, 2025
We were running into the same issue with the following output:
The job for this is
While trying to provide a small
cspell.jsonthat could reproduce this I found that it was specifically caused by afilesentry in the configuration which looked like the following:Removing that files entry would cause the GitHub action to work as expected. Locally this files configuration already works as expected.
My hypothesis is that this could be a difference between how the GitHub action interprets this vs how CSpell itself does so. Or it's a platform difference (Mac locally; Linux in the CI).
Re-reading the documentation, I suspect that our configuration might be invalid (it's not actually a glob?) but it's not exactly clear to me whether that's true or why it would then still work on our local development machines.