github-community-projects / github-community-projects/issue-metrics
Option to include number of very active reviewers in report
- Dominant language
- Python
- Stars
- 538
- Forks
- 94
- Avg merge
- 49m
- Merged PRs (30d)
- 13
Description
One metric that we found helpful at $dayjob was looking at how many people there are that provide the bulk of mentorship for contributors. If that drops below a certain line (2-3 people minimum) it typically means the project is in danger.
Technically what we do is simple: Compute the number of people that provide at least $n comments over time period $x.
Is there any way to retrieve that kind of information in a/this GitHub action?
Contributor guide
Research direction
No files, tests, or entry points are named. Start by locating the GitHub Action code that gathers and reports issue, pull-request, or discussion metrics, then trace how time periods and per-person comment counts are represented. Done means the action can report how many people meet a configurable comment threshold within a configurable period.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- analytics
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100