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

Add spelling check to GitHub workflow #3623

Merged
merged 5 commits into from
Nov 3, 2024

Conversation

KristjanESPERANTO
Copy link
Contributor

Besides updating cspell and handling spelling issues, the important change is adding the spelling check to the GitHub workflow.

I'm not sure if it will bother us too much when people create PRs. But I wanted to give it a try. Or do you have any other ideas on how we can run the spelling check on a regular basis?

@KristjanESPERANTO KristjanESPERANTO marked this pull request as ready for review November 3, 2024 16:31
@sdetweil
Copy link
Collaborator

sdetweil commented Nov 3, 2024

i saw that the node-ical workflow added coderabbit
which added a codeblock around an example i gave, and improved the text i added in doc

pretty impressive

@khassel
Copy link
Collaborator

khassel commented Nov 3, 2024

Or do you have any other ideas on how we can run the spelling check on a regular basis?

maybe as cronjob as we have already in stale.yaml on develop?

@KristjanESPERANTO
Copy link
Contributor Author

maybe as cronjob as we have already in stale.yaml on develop?

That sounds like a better approach! I added a GitHub workflow to run the spell check a few days before each release.

@khassel khassel merged commit 6ce3622 into MagicMirrorOrg:develop Nov 3, 2024
10 checks passed
@khassel
Copy link
Collaborator

khassel commented Nov 3, 2024

AFAIK the cronjobs needs to be on master wo work so we have to do the spellcheck manually before next release ...

@KristjanESPERANTO
Copy link
Contributor Author

AFAIK the cronjobs needs to be on master

That would be suboptimal. Let's see what the job will do on 27th December 🙂

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

Successfully merging this pull request may close these issues.

3 participants