Linting/Spellchecking workflow
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- tex
- Domain
- documentation
Research direction
No files, tests, or workflow entry points are named. Start by inspecting the repository's TeX sources and existing automation to determine where linting or spellchecking would fit; done means a concrete workflow and its scope are agreed and added.
Written by the indexing model from the issue text.
Description
I will look in to finding a nice one. They are quite handy for catching errors.
- Dominant language
- TeX
- Stars
- 1.4k
- Forks
- 289
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from OpenLogicProject/OpenLogic
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
OpenLogicProject/OpenLogic#339 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 50/100
OpenLogicProject/OpenLogic#436 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
OpenLogicProject/OpenLogic#435 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
OpenLogicProject/OpenLogic#425 · 1 comment ·
-
Improve docsOpen
Difficulty 5/5 Over a week Newbie friendliness 25/100
OpenLogicProject/OpenLogic#390 ·
All issues in OpenLogicProject/OpenLogic
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
chingu-voyages/V62-tier3-team-33#285 ·
Maintainers usually reply within 1 day
-
automated issue report
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
lirantal/discoprint#36 ·
Maintainers usually reply within 1 day
-
accepting PR Content:HTML
Difficulty 1/5 Under an hour Newbie friendliness 88/100
mdn/content#45988 · 1 comment ·
Maintainers usually reply within 1 day
-
[Doc Gap] Document new --enable-public-network-access breaking change for azurebackup vault createOpencopilot documentation
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day