Skip to content
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: Docs markdown linting and spell-checking for PRs #7422

Closed
1 of 3 tasks
SeanKilleen opened this issue Nov 2, 2021 · 8 comments
Closed
1 of 3 tasks

Offer: Docs markdown linting and spell-checking for PRs #7422

SeanKilleen opened this issue Nov 2, 2021 · 8 comments
Labels
area/automation Categorizes an issue or PR as relevant to project automation difficulty/starter 🚀 Categorizes an issue for which the difficulty level is reachable by newcomers project/documentation 📖 Categorizes an issue or PR as relevant to documentation

Comments

@SeanKilleen
Copy link
Contributor

SeanKilleen commented Nov 2, 2021

I thought I would offer this in case it's useful.

I've added markdown linting and spellchecking to the NUnit docs, the akka.net docs, and the Marten docs.

This is typically done by adding a parallel job that runs the node tooling, and all of the corrections that go with a tool (the Akka .NET issue shows how I'd take this step by step).

Proposed Steps

@SeanKilleen SeanKilleen added difficulty/tbd Categorizes an issue for which the difficulty level needs to be defined. triage/untriaged Indicates an issue requires triaging or verification labels Nov 2, 2021
@jeromelaban
Copy link
Member

Thanks Sean! Indeed that would be very interesting!

@jeromelaban jeromelaban added the project/documentation 📖 Categorizes an issue or PR as relevant to documentation label Nov 3, 2021
@Youssef1313
Copy link
Member

Youssef1313 commented Dec 17, 2021

I made a small progress in https://github.com/Youssef1313/uno/tree/markdownlint, anyone is welcome to work on top of it.

GitHub
Build Mobile, Desktop and WebAssembly apps with C# and XAML. Today. Open source and professionally supported. - GitHub - Youssef1313/uno at markdownlint

@SeanKilleen
Copy link
Contributor Author

SeanKilleen commented Oct 6, 2022

I've been meaning to pick this up for a minute. Got the Hacktoberfest email and reminded me of it. Going to start the first PR for this today.

@MartinZikmund
Copy link
Member

@SeanKilleen Are you planning to work on the markdown linting?

@MartinZikmund MartinZikmund added difficulty/starter 🚀 Categorizes an issue for which the difficulty level is reachable by newcomers area/automation Categorizes an issue or PR as relevant to project automation and removed triage/untriaged Indicates an issue requires triaging or verification difficulty/tbd Categorizes an issue for which the difficulty level needs to be defined. labels Jul 19, 2023
@SeanKilleen
Copy link
Contributor Author

@MartinZikmund whoops, sorry about that! I'll bump this back up to the top of my radar.

@MartinZikmund
Copy link
Member

No worries, was just walking through the backlog to make sure issues are still current 😊

@SeanKilleen
Copy link
Contributor Author

@MartinZikmund double-oops! This was already completed in #10080 back in October. It was linked to this but didn't close the issue, and I forgot it was already done because I had done several projects at the same time 😅

Going to go ahead and close this out. 👍

@SeanKilleen
Copy link
Contributor Author

Annnnd re-opening because I realized we're talking about markdown linting and not spelling. 🤦‍♂️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/automation Categorizes an issue or PR as relevant to project automation difficulty/starter 🚀 Categorizes an issue for which the difficulty level is reachable by newcomers project/documentation 📖 Categorizes an issue or PR as relevant to documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants