draft_metrics_row.py cannot refresh a row for a week that already has one
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
Research direction
Start in scripts/draft_metrics_row.py, especially build_row, and trace how --apply writes the metrics row and targets table. Check the existing tests for row generation, then add coverage for --apply --update when the newest row is this week. Done means only computed cells in that row and the other --apply outputs change; hand-written cells remain intact.
Written by the indexing model from the issue text.
Description
Where: scripts/draft_metrics_row.py (build_row).
Current gap: A sweep late in the week needs the existing row updated (for example W45's contributors and forks after a pull request merged), but the script refuses with already for 2026-W45 and the figures, the row and the targets table are edited by hand.
Suggested approach: Add --update that rewrites the newest row (and the other places --apply writes) when it is for the current week, keeping its hand-written cells.
Done when: --apply --update on a file whose newest row is this week changes only that row's computed cells, covered by a test.
- Dominant language
- HTML
- Stars
- 47
- Forks
- 45
- Avg merge
- 2h 45m
- Merged PRs (30d)
- 93
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
-
check_contributors.py --stub always lists new people under Contributor tooling & docsPossibly taken @yangwenjie304 claimed this today. Opencommunity enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
yakew7/Fair-Code#1294 · 2 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
ci enhancement tooling
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
enhancement tooling
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
ci enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
enhancement good first issue tooling
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
All issues in yakew7/Fair-Code
Similar issues
-
author-page correction
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
acl-org/acl-anthology#10808 · 1 comment ·
Maintainers usually reply within 1 day
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug good first issue priority: medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
TMHSDigital/Free-Game-Dev-Assets#246 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
endoflife-date/endoflife.date#11558 · 1 comment ·
Maintainers usually reply within 1 day
-
gizmo field errorOpenbug frontend: gizmo
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
yt-project/yt#5631 ·
Maintainers usually reply within 1 day