The weekly contributors issue does not give the command to start each new entry
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
Research direction
The issue body is built in contributors_issue_body in scripts/update_weekly_issue.py, so start there and find where the no entry yet authors are listed. The exact stub command is python3 scripts/check_contributors.py --stub LOGIN, so check how that script is invoked before writing the line. Done when each author without an entry gets one stub command line, authors with entries get none, and a test covers both cases.
Written by the indexing model from the issue text.
Description
Where: scripts/update_weekly_issue.py (contributors_issue_body).
Current gap: For someone with no entry yet the issue says to add or update their entry, but not how; check_contributors.py --stub LOGIN now starts it and the person writing the entry has to look the command up.
Suggested approach: Add a line to the issue body for each no entry yet author with the exact python3 scripts/check_contributors.py --stub LOGIN command.
Done when: the body contains one stub command per author without an entry and none for the others, covered by a test.
- Dominant language
- HTML
- Stars
- 47
- Forks
- 45
- Avg merge
- 3h 24m
- Merged PRs (30d)
- 101
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 good first issue tooling
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
The pre-commit hooks lack the issue-reference, traction and contributors checks that make lint runsOpenenhancement tooling
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
documentation good first issue testing
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug community tooling
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
community enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
All issues in yakew7/Fair-Code
Similar issues
-
area:ci phase:dev priority:p1 type:chore
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
init --global under pnpm without pnpm setup hides the cause and suggests the same failing commandOpenb:minor bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
software-mansion/argent#1770 ·
Maintainers usually reply within 1 day
-
auto:producer auto:security
Difficulty 1/5 Under an hour Newbie friendliness 88/100
fritzprix/libr-agent#2594 ·
Maintainers usually reply within 1 day
-
status/need-triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
podman-desktop/podman-desktop#20059 ·
Maintainers usually reply within 1 day
-
help wanted Idea 💡 wdio-cli
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
webdriverio/webdriverio#16361 · 2 comments ·
Maintainers usually reply within 1 day