check_contributors.py --stub starts every entry with only PR titles
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 79/100
Research direction
Read scripts/check_contributors.py, especially stub_entry, and inspect how the script currently obtains merged PR titles. Add tests for a PR body with a Summary and one without; the issue does not name a test file. Done means the stub includes the first Summary line or bullet when present and falls back to the title when absent.
Written by the indexing model from the issue text.
Description
Where: scripts/check_contributors.py (stub_entry).
Current gap: The stub lists each merged PR's number and title and a TODO sentence, but the pull requests of the last two sweeps had a Summary section saying what changed, so the person writing the entry still reads every PR to say it.
Suggested approach: Fetch each PR body (gh pr view --json body) and put the first line or bullet of its Summary under the title, falling back to the title when there is none.
Done when: a stub for a PR with a Summary shows that line, and one without shows only the title, covered by tests.
- Dominant language
- HTML
- Stars
- 47
- Forks
- 45
- Avg merge
- 2h 47m
- Merged PRs (30d)
- 92
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
-
community enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
enhancement good first issue tooling
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
ci enhancement tooling
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
community enhancement tooling
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
bug testing
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
All issues in yakew7/Fair-Code
Similar issues
-
Document and enforce pull request review guidelinesPossibly taken @dashorst claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
bug implicit-state
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Misleading 'Update → Config → Hyprland' menu item silently resets user configs without confirmationOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Tencent/tdesign-react#4465 · 1 comment ·
Maintainers usually reply within 1 day