draft_metrics_row.py --note leaves out the issues the local commits are about to close

Open Beginner friendly
  • Is something wrong?
#1,304 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
84/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
python
Domain
tooling

Research direction

Start in scripts/draft_metrics_row.py, reading draft_note and fetch_closed_issues to see how --pending-closes finds open issues named in local commits. Add the pending issue numbers and titles to the note with a closing-on-merge marker. Done when a test using saved data confirms every issue the sweep fixes appears in the draft.

Written by the indexing model from the issue text.

Description

community enhancement tooling

Where: scripts/draft_metrics_row.py (draft_note, fetch_closed_issues).

Current gap: --pending-closes counts the open issues named by Closes #N in the commits ahead of the base, but --note lists only issues already closed this week, so a sweep note written before the push misses all of its own issues.

Suggested approach: With --pending-closes, add the open issues the local commits close (number and title) to the note's list, marked as closing on merge.

Done when: the draft names every issue the sweep fixes, 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.