CONTRIBUTORS.md is behind the merged pull requests (weekly check)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 88/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- python
- Domain
- documentation
Research direction
Start with CONTRIBUTORS.md and the named script, scripts/check_contributors.py. Run the three --stub ... --commits commands from the issue, add or update each contributor entry, move the snapshot line to the newest merged PR, then run --fix and --commits. Done when the next weekly check reports nobody pending.
Written by the indexing model from the issue text.
Description
The weekly check_contributors.py --pending run found people who merged pull requests after the snapshot in CONTRIBUTORS.md:
- pvarchanavijay: 1 merged PR(s) after the snapshot (#1310); no entry yet
- #1310 Fix pending closes in draft metrics noteFix pending closes in draft metrics note
- ranjanasri6: 1 merged PR(s) after the snapshot (#1311); no entry yet
- #1311 Handle empty groups in significance calculations
- renuvenugopal178: 1 merged PR(s) after the snapshot (#1313); no entry yet
- #1313 Allow configurable generated-files builder timeout
Start the entry of each person with no entry (this also moves the snapshot, sorts and lists them in an area row):
python3 scripts/check_contributors.py --stub pvarchanavijay --commitspython3 scripts/check_contributors.py --stub ranjanasri6 --commitspython3 scripts/check_contributors.py --stub renuvenugopal178 --commits
Add or update their entries, move the snapshot line to the newest merged PR and run python3 scripts/check_contributors.py --fix (then --commits to check commit counts). This issue closes itself on the next weekly run once nobody is pending.
- Dominant language
- HTML
- Stars
- 47
- Forks
- 45
- Avg merge
- 2h 50m
- Merged PRs (30d)
- 85
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
-
community
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
check_contributors.py --stub cannot write the closing issue numberPossibly taken @obethgeoff10c-ops claimed this 1 day ago. Opencommunity enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
yakew7/Fair-Code#1308 · 2 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
community enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Maintainers usually reply within 1 day
-
The generated-files builder timeout cannot be changedPossibly taken @renuvenugopal178 claimed this 3 days ago. Openenhancement good first issue tooling
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
yakew7/Fair-Code#1306 · 3 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
ci enhancement tooling
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
All issues in yakew7/Fair-Code
Similar issues
-
release
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
MichaelYcJo/SpecSeal#1535 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
paperclipai/paperclip#20942 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
cadence-workflow/cadence-ai-samples#174 ·
Maintainers usually reply within 1 day
-
docs
Difficulty 1/5 1-3 hours Newbie friendliness 69/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100