check_contributors.py --pending does not show which issues each pull request closes
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 86/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github, python
- Domain
- cli, developer-experience
Research direction
Start with run_pending in scripts/check_contributors.py and pending in scripts/contributors_entries.py; trace how pending pull requests and commit authors are fetched. Add the closing issue references to each PR’s pending output, then run the relevant test with saved data. Done when a PR that closes issue #1304 displays closes #1304 under its title in --pending.
Written by the indexing model from the issue text.
Description
Where: scripts/check_contributors.py (run_pending), scripts/contributors_entries.py (pending).
Current gap: --stub now writes closing issue #N from GitHub's closingIssuesReferences (#1308), but the pending list and the weekly contributors issue show only the PR number and title, so whoever updates an existing contributor's entry (a count to update line) still looks the issue up by hand.
Suggested approach: Fetch the closing issues for the pending PRs the same way as the commit authors and print closes #N after each PR title.
Done when: --pending shows closes #1304 under a PR that closes it, covered by a test with saved data.
- Dominant language
- HTML
- Stars
- 47
- Forks
- 45
- Avg merge
- 2h 49m
- Merged PRs (30d)
- 69
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 tooling
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
The weekly external-links issue counts the 403 links with no archive copy but does not list themOpenci enhancement tooling
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
enhancement reproducibility tooling
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
enhancement good first issue testing
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
check_contributors.py --stub does not say when a pull request's commit is authored by someone elseOpencommunity enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
All issues in yakew7/Fair-Code
Similar issues
-
site-bug triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
omacom/omarchy#19217 · 1 comment ·
Maintainers usually reply within 1 day
-
`read_nexus` entry point points to a function that no longer existsPossibly taken @RubelMozumder claimed this today. Openannotator bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
FAIRmat-NFDI/pynxtools#876 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
opencode-native panics on session ID after a multibyte characterPossibly taken A pull request linked to this issue is open or already merged. Openarea/tui platform/macos status/repro-plausible type/bug version/v2
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
anomalyco/opencode#64389 · 1 comment ·
Maintainers usually reply within 1 day