check_traction.py cannot notice that the traction numbers are stale against GitHub
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 76/100
Research direction
Start with scripts/check_traction.py and inspect the weekly report workflow to see how the check runs; the issue also names METRICS.md, README.md, and ROADMAP.md as the files being compared. Review the existing offline check first, then run it and compare its behavior with the supplied gh api command. Done means the opt-in --live check reports each differing figure while the offline default remains unchanged.
Written by the indexing model from the issue text.
Description
Where: scripts/check_traction.py, METRICS.md, README.md, ROADMAP.md.
Current gap: The check compares the three files only with each other, so all three can agree and still be wrong. This sweep found stars at 52 in all three while GitHub said 53.
Repro:
$ python3 scripts/check_traction.py # passes
$ gh api repos/yakew7/Fair-Code --jq .stargazers_count # 53, files say 52
Suggested approach: Add an opt-in --live flag that reads stars, forks and watchers (and contributors without bots) from gh api and reports each difference; run it in the weekly report workflow rather than in make lint.
Done when: --live names every figure that differs from GitHub, and the offline default is unchanged.
- Dominant language
- HTML
- Stars
- 47
- Forks
- 45
- Avg merge
- 3h 8m
- Merged PRs (30d)
- 96
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
-
ci enhancement testing
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
enhancement reproducibility tooling
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
enhancement reproducibility
Difficulty 2/5 1-3 hours Newbie friendliness 84/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
-
The benchmark OG card and the home card hard-code counts and domains that are also kept elsewhereOpenenhancement tooling
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
All issues in yakew7/Fair-Code
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
bug raised-by:desk
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
medici-finance/assay#4723 ·
Maintainers usually reply within 1 day
-
[doc-healer] DDUw improvement: retry integrity-filtered issue reads with direct single-item lookupsOpenautomation documentation
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
cline/mcp-marketplace#3334 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
diegosouzapw/OmniRoute#18387 ·