We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
check
Make spelling check conform to check target pattern
Currently Spelling checks are independent of our standard CI pipeline.
We still need the ability to efficiently run the check locally.
But in CI we can use a standard check target for these and then remove the github action which is triggering these.
This will help better align our CI pipeline and reduce the number of github actions we need to enforce.
We would also need to add Spelling guide, which is be a part of this ticket. This ticket also includes updating both: https://github.com/input-output-hk/catalyst-voices https://github.com/input-output-hk/hermes
To use the update check target, each will need a new issue raised to track this issue, and for the PR in those repos to be raised against that Issue.
The text was updated successfully, but these errors were encountered:
apskhem
Successfully merging a pull request may close this issue.
Summary
Make spelling check conform to check target pattern
Description
Currently Spelling checks are independent of our standard CI pipeline.
We still need the ability to efficiently run the check locally.
But in CI we can use a standard check target for these and then remove the github action which is triggering these.
This will help better align our CI pipeline and reduce the number of github actions we need to enforce.
We would also need to add Spelling guide, which is be a part of this ticket.
This ticket also includes updating both:
https://github.com/input-output-hk/catalyst-voices
https://github.com/input-output-hk/hermes
To use the update check target, each will need a new issue raised to track this issue, and for the PR in those repos to be raised against that Issue.
The text was updated successfully, but these errors were encountered: