-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create a WP-CLI command reports GitHub pull request stats #13492
Comments
Going to pick this up over the next couple or few weeks (unless someone wants to hack on it before me). One important qualifying question: if we only picked five (5) of these metrics, which would be the most important? |
As to your question regarding what are the top 5 metrics, for the weekly meeting 7 days is your reporting period
To measure sucess of activities to increase number reviewers
oops not five per se... but it gives a fast overview:-) |
Closing for now. |
Following up on #13441 (comment), I'd like to create a WP-CLI command that generates some top-level GitHub pull request stats we want to track.
Currently, here are the metrics I'm thinking of:
As a v1, this WP-CLI command would fetch data from the GitHub API, process it, and spit out a JSON report. We could put the JSON into some other system for tracking this data over time, or build a simple web page that presents this data in a human-readable format.
Feel free to weigh in with any additional metrics you think are worth tracking, or whether you'd change the ones I've identified. The challenge with metrics is that people tend to optimize for them over time. We'll want to make sure what we track is actually worth optimizing for.
The text was updated successfully, but these errors were encountered: