-
Notifications
You must be signed in to change notification settings - Fork 64
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
Feature: Add Documenation Linting to CI/CD #178
Comments
That would be helpful @nickytonline! :) |
I can definitely implement this, but if someone else wants to take it on, go for it. If not, I'll get around to this during Hacktoberfest at some point. |
I wanted to do it for Hacktoberfest but was not sure what to put @nickytonline. |
Unassigning you for the moment @CBID2 as the PR has been open since October 2023. If you decide to pick this up again, feel free to assign yourself. |
Hey @nickytonline. I still have to figure out a way to configure the action. |
.take |
Thanks for taking this on! If you have not already, join the conversation in our Discord |
Good luck @ebanner! :) Take a look at my test repo here to see what I tried to do. |
Thanks for being interested in this issue. It looks like this ticket is already assigned to a contributor. Please communicate with the assigned contributor to confirm the status of the issue. |
Cool @CBID2, thanks! I'm looking specifically to see if I can get vale to check for undefined abbreviations. In your research, did you see if that is possible? |
I found a plugin to textlint that seems to do what we want https://github.com/textlint-rule/textlint-rule-unexpanded-acronym It also occurs to me since our use case is narrow, we could just roll our own custom script if the overhead of a linter is too big |
Looks pretty possible to me @ebanner! :) How can we go about the creating the custom script? |
Ha the custom script route would just be writing like a python script 🙃 |
Ok so I ran textlint-rule-unexpanded-acronym on
@BekahHW @nickytonline how useful does this output look? What do you guys think? |
@ebanner it looks like it's grabbing all the caps words, which means it's grabbing some words that are caps for emphasis. PR would fall under there and that would be great, but I'm not sure about it grabbing all the words. |
With that in mind, I think it would help if the linter focused on PRs that had incorrect Markdown syntax. What do you think @BekahHW? |
Type of feature
📦 Chore
Current behavior
Currently there is nothing checking for stuff like an acronym being used before it's defined in documentation.
I came across this while reviewing #177
Suggested solution
It made me think of the docs linting we used at Netlify. I think this could be a great addition to maintaining our docs. More about it here, https://www.netlify.com/blog/a-key-to-high-quality-documentation-docs-linting-in-ci-cd/
Additional context
No response
Code of Conduct
Contributing Docs
The text was updated successfully, but these errors were encountered: