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
Is your enhancement related to a problem? Please describe.
https://github.com/crate-ci/typos/blob/master/docs/github-action.md exists as a decent option for us to consider integrating on its own across projects, but perhaps having that as an additional feature in the repo automator set of tools might be useful? I'm not certain if using the Typos action and adding another check to our repos is best or adding additional run time to the repo-automator check is best, so something to consider here but in any case ideal to run a spellchecker against the existing codebases to cleanup and then catch any newly introduced spelling errors.
Thanks for opening the issue, @jeffpaul. I have looked into this and also experimented with the typos action on one of our repositories. Based on my findings, I believe that directly using the action on our repository is a clearer approach (we just need to add one job here). Please let me know if you'd like me to set it up across all of our OSS project repositories.
Please let me know if you'd like me to set it up across all of our OSS project repositories.
@iamdharmesh perhaps start with adding to ClassifAI and then we can have @vikrampm1 help replicate issues across our other repos for others to help work on?
Is your enhancement related to a problem? Please describe.
https://github.com/crate-ci/typos/blob/master/docs/github-action.md exists as a decent option for us to consider integrating on its own across projects, but perhaps having that as an additional feature in the repo automator set of tools might be useful? I'm not certain if using the Typos action and adding another check to our repos is best or adding additional run time to the repo-automator check is best, so something to consider here but in any case ideal to run a spellchecker against the existing codebases to cleanup and then catch any newly introduced spelling errors.
cc: @szepeviktor for the idea in 10up/safe-redirect-manager#407
Designs
No response
Describe alternatives you've considered
cc:
Code of Conduct
The text was updated successfully, but these errors were encountered: