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
Offer: add automated spell-check & markdown linting to docs via GitHub Actions #5460
Comments
Sounds great! Please feel free to go for it :) |
Can this be closed? |
@michaelstaib that depends. Spell-checking is the only thing that's been done. Was going to consider adding markdown-lint and then fixing all the markdown issues as well, or at least writing it up so that somebody could. If you're less interested in that, that's ok; feel free to close it. 👍 |
Its good ... feel free to go ahead :) was just keeping track if it was completed with your PR. Your contributions are welcome and we appreciate the work you have already done! |
@SeanKilleen Are you likely to proceed with this, or shall we close it? 🙂 |
@glen-84 thanks for the ping! I'll see if I can get into it soon. |
Is your feature request related to a problem?
It is related to an ask in the docs that mentions folks can help by spotting typos etc.
The solution you'd like
I've used this technique for a few repos, including the NUnit dcos, the Marten docs, and my blog.
Essentially:
Then at the end, you're left with material improvements + the ability to spot issues later.
Let me know if you're up for this, and I'd be happy to adapt what I've already done to benefit your docs too.
Product
Hot Chocolate
Progress
The text was updated successfully, but these errors were encountered: