pull-request-stats VS pullmetry

And if the quality of the code is a rather difficult thing to calculate, then the quality and speed of reviewing of pull requests can be calculated. In our company, we started using a pull request stats package that integrates with github actions and publishes review statistics directly in pull requests. But we had some issues and incorrect calculations.

Hence my suggestion, if your product saves me $500/seat/month then I'll gladly pay $50/seat/month.

Wordpress is a great example, rather than build another Wordpress, solve one problem Wordpress doesn't solve (example: Elementor) and do it far better (depth vs breadth).

We are using this Github Action (https://github.com/flowwer-dev/pull-request-stats) for now, it adds stats to every PR, it has helped the team visualize their contributions and how critical it was for us moving forward and as a manager/tech-lead it helps me identify areas of improvements at the individual level. I think it's a simple idea with a lot of depth.

A Github action to print relevant stats about the pull request reviewers in team: https://github.com/flowwer-dev/pull-request-stats

We thought that those library technically can not meet our needs, then why not make our own web service, for example with Ruby on Rails, a couple of weeks of work and we had the PullKeeper — open source application for getting relevant statistics about PRs, reviewers and comments. Now all statistics can be collected in one place, conveniently divided into statistics for individual repositories and for the whole company.

you can setup local production environment and run local server in production mode, you can check example in my repo https://github.com/kortirso/pullmetry

In addition to using the PullKeeper, you can safely take the source codes (and don’t forget to star repository) of the application and use them locally or run them on your server only for you. So please welcome and I will be glad if you start using PullKeeper.