Report CONTRIBUTORS.md drift in a weekly workflow instead of finding it by hand
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 52/100
Research direction
Start by reading scripts/check_contributors.py and the existing .github/workflows/traction-live.yml workflow; check how merged PR authors are selected and how the workflow updates issues. Add a weekly workflow that keeps one issue current with authors missing from CONTRIBUTORS.md and closes it when the file is updated. Done means the issue lists newly merged PR authors and closes after the snapshot includes them.
Written by the indexing model from the issue text.
Description
Where: .github/workflows/, scripts/check_contributors.py.
Current gap: check_contributors.py runs only in make lint and is skipped without gh, so a missed contributor after a merge is noticed at the next manual sweep.
Suggested approach: Add a weekly workflow like traction-live.yml that runs the script against merged PRs after the snapshot and keeps one issue up to date with the authors that have no entry yet.
Done when: the issue lists new merged-PR authors and closes itself when the file is updated.
- Dominant language
- HTML
- Stars
- 47
- Forks
- 45
- Avg merge
- 3h 15m
- Merged PRs (30d)
- 108
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 85/100
Maintainers usually reply within 1 day
-
enhancement testing tooling
Difficulty 2/5 1-3 hours Newbie friendliness 85/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
-
bug documentation
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
ci enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
All issues in yakew7/Fair-Code
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:tooling bug P3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
agent/sec-check security stage/010-actionable
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
cncf/endusers#2030 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 2 days
-
Install notes print "Camunda REST API: https://" without a host when global.host is setPossibly taken @irisfield claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
camunda/camunda-platform-helm#7790 ·
Maintainers usually reply within 1 day