check_contributors.py --stub cannot write the closing issue number

Open Beginner friendly
  • Is something wrong?
#1,308 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
github, python
Domain
tooling

Research direction

Start with scripts/check_contributors.py, especially stub_entry, and inspect how it currently formats merged PR entries. Look at the gh pr view --json closingIssuesReferences output and add a test using saved data for a PR with a closing issue. Done when the stub includes that issue number and omits the closing issue text when there are no references.

Written by the indexing model from the issue text.

Description

community enhancement

Where: scripts/check_contributors.py (stub_entry).

Current gap: Entries end with (#PR, closing issue #N), which the author types from the PR page, but GitHub already knows it: gh pr view --json closingIssuesReferences.

Suggested approach: Look up the closing issue references of each merged PR and write closing issue #N in the stub, leaving it out when there are none.

Done when: a stub for a PR that closes an issue includes the number, covered by a test with saved data.

Dominant language
HTML
Stars
47
Forks
45
Avg merge
2h 47m
Merged PRs (30d)
92

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from yakew7/Fair-Code

All issues in yakew7/Fair-Code

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.