-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
feat: Installing vale(redo) #2104
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
Conversation
Signed-off-by: Christine Belzie <[email protected]>
|
@CBID2 is attempting to deploy a commit to the Arc53 Team on Vercel. A member of the Team first needs to authorize it. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2104 +/- ##
==========================================
+ Coverage 42.28% 43.66% +1.37%
==========================================
Files 136 140 +4
Lines 9315 9860 +545
==========================================
+ Hits 3939 4305 +366
- Misses 5376 5555 +179 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
This comment was marked as spam.
This comment was marked as spam.
Hi @Pranavi125! You've replied to a Pull Request. Not an issue 😁 |
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
This PR introduces a new documentation quality check using Vale, a powerful linter for prose. This is a redo of the original PR feat: add Vale linter configuration and GitHub Action workflow #2102, which initially set up Vale via GitHub Actions but some configuration adjustments prevented me from continuing with that version.
Why was this change needed? (You can also link to an open issue here)
Other information:
Closes 🚀 Feature: add vale Linter for documentation maintenance #2099