Hi all!
Today I want to show you something I've been working on lately, and ask for any feedback and ideas about the next steps :)
I've built a web app that analyzes repositories on GitHub and shows them on a dashboard like this one of Rails or the one of dev.to.
The initial idea was to give a comfortable view of the team's performance, raise possible issues and present insights.
Since GitHub bought a competitor in that field that offered similar features, I'm pivoting slightly to present comparison between different repositories and considering my next steps.
Going forward, I'm thinking the following can be useful to get the most out of what I built thus far and offer value:
Badges repositories can add to their README page for merge rate, average response times and etc.
Personal rankings for contributors: average review cycles, how often their pushes fail tests, improve coverage, PR sizes and so on.. things that should encourage a better way of working.
Smarter Insights - where are the problematic areas in the codebase based on how quickly PRs of that area are merged, how many review cycles it takes and so on..
Rankings of open-source projects: I'm on the fence about this one. I don't want to rank open-source projects based on how quickly PRs are addressed or issues are resolved, but I'm trying to figure out a way for making maintainers' life easier and proud of their work.
What do you think?
Oh yea, did you know that dev.to has a merge rate of 91%?
Top comments (6)
Really neat!
It’s nice to see this going down over time.
Yep!
Do you think open-source maintainers care about this metric as much as team-leaders in a company with a private codebase?
That's a really great tool, but is it a useful metric? It could depend a lot on the quality of the PR
Yep. This is something to be implemented in the future :)
Sounds like a great idea!
Thank you!