Option to include number of very active reviewers in report

Open
#114 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
github-actions, python
Domain
analytics

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.

Description

enhancement good first issue keep

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?

Dominant language
Python
Stars
542
Forks
94
Avg merge
10h 3m
Merged PRs (30d)
9

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github-community-projects/issue-metrics

All issues in github-community-projects/issue-metrics

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.