Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

no-files-to-check error when using only_check_changed_files and only changing GitHub actions #61

Open
gwarf opened this issue Nov 14, 2023 · 3 comments
Milestone

Comments

@gwarf
Copy link

gwarf commented Nov 14, 2023

Hi,
We are using the Check Spelling as a GitHub action, and we are getting no-files-to-check errors when using only_check_changed_files and when pushing changes touching only GitHub actions.
We are not making use of only or excludes, and in fact I wouldn't mind when there are no files to check, that no error would be reported.
I saw that there were settings like warnings, but if possible I wouldn't want to have to specify the full lists of warnings, as it doesn't seem convenient in case new ones are added/removed.
Have you any suggestion on how to address this?
Thanks for your work!

@jsoref
Copy link
Member

jsoref commented Nov 14, 2023

Yeah, I'm noticing that. I'll probably add a new thing to allow overriding specific items instead of just the whole set. Thanks for your feedback.

@jsoref
Copy link
Member

jsoref commented Nov 14, 2023

In the interim, you'll indeed have to use warnings, e.g.:

warnings: bad-regex,binary-file,deprecated-feature,ignored-expect-variant,large-file,limited-references,no-newline-at-eof,noisy-file,non-alpha-in-dictionary,token-is-substring,unexpected-line-ending,whitespace-in-dictionary,minified-file,unsupported-configuration,no-files-to-check

Sorry...

@gwarf
Copy link
Author

gwarf commented Nov 14, 2023

OK, thanks for feedback!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants