make key-fold-check is undocumented and nothing checks that every Makefile target is described
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript, python
- Domain
- build-system, documentation
Research direction
Start with the ## description lines in the Makefile and the list of make commands in CONTRIBUTING.md, then find where key-fold-check is defined to see what it checks. Add a CONTRIBUTING.md line for make key-fold-check, and add a test that parses the Makefile for described targets and fails when one is missing from CONTRIBUTING.md, skipping help. Done when adding a new described target without a CONTRIBUTING line makes that test fail.
Written by the indexing model from the issue text.
Description
Where: CONTRIBUTING.md, Makefile.
Current gap: Every documented target is listed in CONTRIBUTING except help and key-fold-check, so the check that the JS case-folding table still matches Python is not mentioned where contributors look.
Suggested approach: Document make key-fold-check and add a test that each target with a ## description appears as make <target> in CONTRIBUTING (with help as the one exception).
Done when: the test fails when a new target is added without a CONTRIBUTING line.
- Dominant language
- HTML
- Stars
- 47
- Forks
- 45
- Avg merge
- 3h 24m
- Merged PRs (30d)
- 101
Getting set up
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 yakew7/Fair-Code
-
enhancement good first issue tooling
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
ci community enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
The pre-commit hooks lack the issue-reference, traction and contributors checks that make lint runsOpenenhancement tooling
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug community tooling
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
community enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
All issues in yakew7/Fair-Code
Similar issues
-
post-v4
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
openSUSE/rpm-config-SUSE#98 ·
-
Bump calamine to 0.38: RUSTSEC-2026-0436 (CFB/OLE2 panic and unbounded allocation) fails cargo auditOpen
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
docling-project/docling.rs#979 ·
Maintainers usually reply within 1 day
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
JdeRobot/RoboticsInfrastructure#843 ·
Maintainers usually reply within 1 day