Nothing checks that every contributor entry appears in the Contributions by area table
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
Research direction
Start with scripts/check_contributors.py and the Contributions by area table in CONTRIBUTORS.md. Add a check that every non-deleted contributor handle appears in at least one area row, and report the handles that are missing. Done means the script exits with a failure when an entry is absent from the table and passes on the current file.
Written by the indexing model from the issue text.
Description
Where: CONTRIBUTORS.md, scripts/check_contributors.py.
Current gap: The area table is edited by hand when a person is added (four rows changed in the last sweep) and nothing notices a contributor who is missing from every row.
Suggested approach: Check that each non-deleted entry's handle appears in at least one area row and report the ones that do not.
Done when: the check fails on an entry absent from the table and passes on the current file.
- 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
-
documentation good first issue testing
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
All issues in yakew7/Fair-Code
Similar issues
-
needs-area-label
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gitbutlerapp/gitbutler#16982 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
TransformerLensOrg/TransformerLens#1980 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 79/100