Awesome

Pull Request Stats

Github action to print relevant stats about Pull Request reviewers.

The objective of this action is to:

• Reduce the time taken to review the pull requests.
• Encourage quality on reviews.
• Help to decide which people to assign as reviewers.

Running this action will add a section at the bottom of your pull requests description:

Each reviewer has a link pointing to their historical behavior of each reviewer:

Or send the data to your favorite tools by using the integrations available:

Privacy

• No repository data is collected, stored, or distributed by this GitHub action. This action is state-less.
• Charts data is sent over the URL and never stored or transmitted anywhere else.
• Minimal data is sent to Mixpanel in order to improve this action. However, you can opt-out using the telemetry option.

Usage

Just add this action to one of your workflow files:

      - name: Run pull request stats
        uses: flowwer-dev/pull-request-stats@main

If you are getting an empty table or an error, check the troubleshooting section.

Action inputs

The possible inputs for this action are:

Action outputs

This action outputs the following variables:

Examples

Minimal config

Add this to the file .github/workflows/stats.yml in your repo:

name: Pull Request Stats

on:
  pull_request:
    types: [opened]

jobs:
  stats:
    runs-on: ubuntu-latest
    steps:
      - name: Run pull request stats
        uses: flowwer-dev/pull-request-stats@main

This config will:

• Calculate the reviewer stats for the current repo in the lasts 30 days.
• Add links to the historical data.
• Sort results by the "total reviews" column by default.

and print a table like this:

Visual config

Add this to the file .github/workflows/stats.yml:

name: Pull Request Stats

on:
  pull_request:
    types: [opened]

jobs:
  stats:
    runs-on: ubuntu-latest
    steps:
      - name: Run pull request stats
        uses: flowwer-dev/pull-request-stats@main
        with:
          token: ${{ secrets.ADD_A_PERSONAL_ACCESS_TOKEN }}
          organization: 'piedpiper'
          period: 7
          charts: true
          disableLinks: true
          sortBy: 'totalComments'
          stats: 'totalComments,openedPullRequests'

This config will:

• Calculate the reviewer stats for all the repos in the "piedpiper" organization in the lasts 7 days.
• Display charts for the metrics.
• Remove the links to detailed charts.
• Sort results by the "Total comments" column.
• Show the "Total comments" and "Opened pull requests" columns (in that order).

and print a table like this:

Stats

The stats are calculated as follows:

• Total reviews (totalReviews): The count of all Pull Requests reviewed by a person in the period.
• Time to review (timeToReview): The median time a reviewer takes from the Pull Request publication or the last Commit push (whatever happens last) to the first time the pull request is reviewed.
• Total comments (totalComments): The number of comments made while reviewing other users' Pull Requests during the specified period. Comments made on your own PRs or general PR discussions are excluded; only comments directly related to code are counted.
• Comments per review (commentsPerReview): The average comments the reviewer made on the pull requests.
• Opened pull requests (openedPullRequests): The number of pull requests opened by the user in the period.

Integrations 🔌

Check the guide for the tool you want to integrate:

• Slack
• Microsoft Teams
• Webhooks

Troubleshooting

1. Make sure the repositories have pull request reviews during the configured period.
2. When specifying repositories or organization parameters, a Personal Access Token is required in the token parameter.
3. If providing a Personal Access Token, ensure it has the repo permission for the projects you want.
4. If you are not providing a Personal Access Token (thus, the action is using the default GITHUB_TOKEN), make sure the job has the contents: read and pull-requests: write permissions While these permissions are typically provided by default, certain organizations may customize or overwrite them.

jobs:
  stats:
    runs-on: ubuntu-latest
    permissions:
      contents: read
      pull-requests: write
    steps:
      - name: Run pull request stats
        uses: flowwer-dev/pull-request-stats@main

This error happens when the organization configures the action's permissions as read. To fix it, overwrite them by adding a permissions configuration in the workflow file. The minimum required permissions are contents: read and pull-requests: write:

jobs:
  stats:
    runs-on: ubuntu-latest
    permissions:
      contents: read
      pull-requests: write
    steps:
      - name: Run pull request stats
        uses: flowwer-dev/pull-request-stats@main

1. Check the sponsorship comes from the account that owns the configured repos (usually an organization).
2. Make sure the sponsorship is configured as public, otherwise, the action cannot access the sponsorship information. If you prefer to keep it private, please reach me out to make it work for you that way 😉.

Premium features ✨

This action offers some premium features only for sponsors:

• Disabling telemetry.
• Slack integration.
• Microsoft Teams integration.
• Coming soon: Discord integration, web version.

The suggested sponsorship is $20 USD / month. However, if it's not possible for you or your organization, please consider supporting it with any amount you can. Even a one-time sponsorship will enable the Premium features and encourage the progress of this project.

Being a sponsor will also give you access to the premium features in all of my other projects.

Thanks for your support! 💙

Related projects 🔥

• Recap: Tired of writing pull request descriptions? Let GPT do it for you.

Used by

Used by hundreds of successful teams:

Authors

Help

This project is maintained by a small team, considering supporting the project by:

• ⭐ Star this repo.
• Sharing your feedback.
• Joining the community.
• Becoming a sponsor.

NEW: Check the web version! ⚡

<img alt="Flowwer web preview" src="/assets/web-preview.png" />

Breaking News! We’ve unleashed the stand-alone version of this action!

• Filter by repositories and date range.
• Stats tracking over the time.
• Tons of new features coming soon!

<img alt="Sign up to Flowwer" height="42px" src="/assets/signup-btn.png" />

License

MIT