Pull request analytics action

This GitHub Action measures metrics for developers and/or teams. Reports are generated in issues based on user actions such as opening/closing pull requests, requesting/conducting reviews, opening discussions, and more. The action is designed to provide better insights into team strengths and identify bottlenecks.

Motivation

pull-request-analytics-action addresses several key challenges:

Identifying Bottlenecks in Code Review Processes: Easily generate summaries showing where delays occur in the review stages.
Tracking Trends in Code Review Processes: Analyze how review dynamics change over time to identify positive or negative trends.
Detecting Significant Deviations: Identify metrics that vary significantly among teams and developers, revealing potential areas of concern.
Simplifying Analysis of Notable PRs: Provides a list of standout pull requests, helping you focus on the most critical cases.

Overall, this action enables faster and more accurate assessments, leading to better decision-making.

Metrics

All metrics are presented in the form of tables, charts, and lists (Report example). Below, you can see an example of such data.

Lead Time

Displays the time from PR creation to each displayed status. Helps identify bottlenecks in the code review process. Use the timeline value in the SHOW_STATS_TYPES parameter.

user	Time in draft	Time to review request	Time to review	Time to approve	Time to merge	Total merged PRs
dev1	34 minutes	17 minutes	3 hours 34 minutes	7 hours 32 minutes	14 hours 9 minutes	22
dev2	21 minutes	20 minutes	4 hours	4 hours	23 hours 1 minute	13
dev3	15 minutes	18 minutes	15 hours 16 minutes	24 hours 7 minutes	53 hours 43 minutes	2
total	27 minutes	18 minutes	4 hours 21 minutes	7 hours 36 minutes	26 hours 14 minutes	47

gantt
title Pull requests timeline(percentile75) 12/2023 / minutes
dateFormat X
axisFormat %s
section dev1
Time in draft(34 minutes) :  0, 34
Time to review request(17 minutes) :  0, 17
Time to review(3 hours 34 minutes) :  0, 214
Time to approve(7 hours 32 minutes) :  0, 452
Time to merge(14 hours 9 minutes) :  0, 849

section dev2
Time in draft(27 minutes) :  0, 21
Time to review request(12 minutes) :  0, 20
Time to review(4 hours) :  0, 240
Time to approve(4 hours) :  0, 240
Time to merge(23 hours 1 minute) :  0, 1381

section dev3
Time in draft(27 minutes) :  0, 15
Time to review request(12 minutes) :  0, 18
Time to review(15 hours 16 minutes) :  0, 916
Time to approve(24 hours 7 minutes) :  0, 1447
Time to merge(53 hours 43 minutes) :  0, 3223

section total
Time in draft(27 minutes) :  0, 27
Time to review request(12 minutes) :  0, 18
Time to review(4 hours 21 minutes) :  0, 261
Time to approve(7 hours 36 minutes) :  0, 456
Time to merge(26 hours 14 minutes) :  0, 1574

Loading

pie
title Review time total 12/2023
"0-1 hours(12)":12
"4-6 hours(7)":7
"6-9 hours(4)":4
"12+ hours(2)":2

Loading

Contribution

Shows the total volume of code merged, reviews conducted, and comments in PRs. Helps to understand the context in which other metrics apply. Use the workload value in the SHOW_STATS_TYPES parameter.

user	Total opened PRs	Total merged PRs	Total reverted PRs	Additions/Deletions	PR size: xs/s/m/l/xl	Total comments
dev1	24	22	1	+1448/-3110	14/5/4/0/1	41
dev2	14	13	0	+813/-2062	7/4/1/2/0	6
dev3	2	2	0	+15/-3	2/0/0/0/0	1
total	50	47	1	+8530/-10137	30/9/6/2/3	71

Discussion Intensity (Author’s Perspective)

Measures how discussion-heavy PRs are from the author's perspective, based on open discussions, review statuses, and the number of comments. Additionally, you can track discussion topics and user agreement by adding discussion topics in [[]] and using thumbs up/down ( 👍 / 👎 ) reactions on the opening comment. Use the pr-quality value in the SHOW_STATS_TYPES parameter.

user	Total merged PRs	Changes requested received	Agreed / Disagreed / Total discussions received	Comments received
dev1	22	3	0 / 0 / 10	20
dev2	13	1	0 / 0 / 2	3
dev3	2	0	0 / 0 / 1	1
total	47	6	3 / 2 / 25	37

pie
title Discussions types total 12/2023
"Bug(12)":12
"Performance(8)":8
"Code complexity(3)":3
"Test coverage(2)":2
"Formatting(9)":9

Loading

Discussion Intensity (Reviewer’s Perspective)

Measures how discussion-heavy PRs are from the reviewer's perspective, based on discussions, comments, and PR statuses. Helps understand reviewer engagement and decision-making. Use the code-review-engagement value in the SHOW_STATS_TYPES parameter and add thumbs up/down ( 👍 / 👎 ) reactions on opening comments.

user	Reviews conducted	Agreed / Disagreed / Total discussions conducted	Comments conducted	PR size: xs/s/m/l/xl	Changes requested / Commented / Approved
dev1	8	0 / 0 / 0	0	5/2/0/1/0	0 / 0 / 8
dev2	20	3 / 2 / 22	33	10/3/4/0/3	5 / 8 / 20
dev3	10	0 / 0 / 2	3	4/2/1/2/1	1 / 1 / 10
total	46	3 / 2 / 25	37	30/9/6/2/3	6 / 12 / 46

Reviewer Response Time

Shows how quickly reviewers respond to review requests. Helps better understand lead time metrics and reviewer engagement. Use the response-time value in the SHOW_STATS_TYPES parameter.

user	Review requests conducted	Reviews conducted	Time from opening to response	Time from initial request to response	Time from re-request to response
dev1	259	88	10 hours 13 minutes	6 hours 37 minutes	2 hours 2 minutes
dev2	271	56	10 hours 48 minutes	9 hours 42 minutes
dev3	218	66	6 hours 59 minutes	6 hours 55 minutes	3 hours 2 minutes
total	1219	282	7 hours 15 minutes	6 hours 41 minutes	1 hour 57 minutes

Metric Trends Over Time

This section displays metric changes over time using graphs, helping to understand how metrics have evolved over extended periods. To enable these graphs, ensure that PERIOD_SPLIT_UNIT is set and that the collected data covers at least two time periods (e.g., quarters or months).

$$\color{dimgrey}Time\ In\ Draft\ \color{firebrick}Time\ To\ Review\ Request\ \color{gold}Time\ To\ Review\ \color{chartreuse}Time\ To\ Approve\ \color{blueviolet}Time\ To\ Merge\ \color{orange}Time\ From\ Initial\ Request\ To\ Response\ \color{violet}Time\ From\ Opening\ To\ Response\ \color{mediumblue}Time\ From\ Rerequest\ To\ Response$$

---
config:
    xyChart:
        width: 900
        height: 600
    themeVariables:
        xyChart:
            titleColor: "black"
            plotColorPalette: "dimgrey, firebrick, gold, chartreuse, blueviolet, orange, violet, mediumblue"
---
xychart-beta
    title "Pull request's retrospective timeline(75th percentile) total"
    x-axis ["4/23", "5/23", "6/23", "7/23", "8/23", "9/23", "10/23", "11/23", "12/23", "1/24", "2/24", "3/24", "4/24", "5/24", "6/24", "7/24", "8/24", "9/24", "10/24"]
    y-axis "hours" 0 --> 47
    line [0, 0, 0, 0, 0, 0, 0.13, 0.12, 0.13, 0.42, 0.23, 0.32, 0.15, 0.08, 0.15, 0.18, 0.13, 0.1, 0.17]
line [0, 0, 0, 0, 0, 0.22, 0.13, 0.12, 0.13, 0.32, 0.23, 0.32, 0.18, 0.08, 0.15, 0.2, 0.13, 0.1, 0.17]
line [0.77, 0.65, 1.52, 2.35, 1.42, 2.52, 3.2, 2.13, 4.7, 2.87, 5.95, 4.75, 5.85, 4.98, 3.05, 2.17, 2.5, 3.58, 5.28]
line [2.28, 4.95, 4.1, 4.6, 4.07, 3.3, 6.82, 5.65, 6.72, 4.08, 6.77, 10.43, 7.18, 9.58, 6.9, 4.2, 7.13, 6.35, 8.05]
line [21.52, 28.9, 23.47, 21.2, 23.63, 24.9, 20.72, 29.22, 26.07, 25.52, 22.33, 46.33, 23.43, 26.47, 17.22, 24.28, 21.32, 22.97, 21.95]
line [0, 1.67, 2.62, 3.8, 2.33, 3.15, 4.8, 2.72, 4.9, 2.6, 5.55, 6.12, 5.75, 5.82, 2.98, 1.68, 2.95, 3.92, 5.6]
line [0.5, 0.75, 2.07, 2.28, 1.4, 2.98, 5.17, 2.52, 4.93, 3.57, 6, 7.22, 6.33, 5.77, 3.62, 2.75, 3.28, 3.9, 5.35]
line [0, 2.18, 0.92, 0.77, 5.47, 0.83, 4.85, 2.42, 4.28, 23.18, 0, 1.63, 1.98, 4.13, 1.32, 1.85, 1.63, 2.5, 6.72]

Loading

List of Notable PRs

Identifies standout pull requests, helping quickly locate the most pending PRs at various stages, the largest and the most commented ones. This facilitates analysis by focusing on the most significant cases. Here is an example of the most commented PRs.

Feature: PR Title 1(example)(31)
Feature: PR Title 2(example)(27)
Feature: PR Title 3(example)(25)

Getting started

To integrate pull-request-analytics-action into your GitHub repository, use the following steps. The provided code is a template and can be adjusted to fit your specific requirements:

Navigate to the .github/workflows directory in your repository.
Create a YAML file, for example, pull-request-analytics.yml.

Open your new YAML file and paste the following example workflow. This is a starting template and you can modify it as needed:

name: "PR Analytics"
on:
  workflow_dispatch:
    inputs:
      report_date_start:
        description: "Report date start(d/MM/yyyy)"
      report_date_end:
        description: "Report date end(d/MM/yyyy)"
jobs:
  create-report:
    name: "Create report"
    runs-on: ubuntu-latest
    steps:
      - name: "Run script for analytics"
        uses: AlexSim93/pull-request-analytics-action@v4
        with:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} # In the case of a personal access token, it needs to be added to the repository's secrets and used in this field.
          GITHUB_REPO_FOR_ISSUE: # Make sure to specify the name of the repository where the issue will be created
          GITHUB_OWNER_FOR_ISSUE: # Make sure to specify the owner of the repository where the issue will be created
          GITHUB_OWNERS_REPOS: # Be sure to list the owner and repository name in the format owner/repo
          CORE_HOURS_START: "9:00"
          CORE_HOURS_END: "19:00"
          TIMEZONE: "Europe/Berlin"
          REPORT_DATE_START: ${{ inputs.report_date_start }}
          REPORT_DATE_END: ${{ inputs.report_date_end }}

Check your repository settings if you want to publish reports in issues. Go to the repository's Settings, and under the Features section, make sure the Issues checkbox is selected. Additionally, if you are collecting statistics for an organization's repository using a personal access token, ensure that the token has the necessary permissions. To do this, go to the organization's Settings and navigate to the Personal access token tab. Verify that the tokens (classic) have permission to access the repository.
Decide on which GitHub event you want to trigger the report generation. You can refer to the GitHub Events Documentation for a detailed understanding of different events. In this example, the workflow_dispatch event is selected to allow the action to be manually triggered multiple times with different parameters. report_date_start and report_date_end can be set before running the action without modifying the code.
Depending on your needs, you can use either the GITHUB_TOKEN or a generated Personal Access Token (classic). In this example, we are using the GITHUB_TOKEN, but keep in mind that it won't allow you to collect data from multiple repositories or organizations, nor will it provide data segmented by GitHub teams. If these features are critical for you, create a token with the repo and read:org scopes selected on tokens page. You can read more about tokens in the GitHub Documentation.
Configure the parameters to suit your needs according to the Parameters Overview section.
Merge the code into the main branch of the repository.
Open the Actions tab and select the created action from the left sidebar. In our case, it's PR Analytics.
In your repository, go to the Actions tab. Select PR analytics and start it via "Run workflow". Fill in any necessary parameters and execute the action. Depending on the number of PRs, it may take from 1 to several minutes to complete.
Open the Issues tab, where you'll find the generated report.

Using GitHub Enterprise Server

pull-request-analytics-action supports integration with GitHub Enterprise Server. To use this feature, you need to set the GITHUB_API_URL environment variable:

In your workflow file, define the GITHUB_API_URL under the env key.
Set the value to your GitHub Enterprise Server API endpoint.

Example:

env:
  GITHUB_API_URL: http(s)://HOSTNAME/api/v3

This configuration allows pull-request-analytics-action to interface with your GitHub Enterprise instance, enabling you to leverage the full capabilities of the action within your enterprise environment.

Configuration Parameters Overview

Below is a table outlining the various configuration parameters available for pull-request-analytics-action. These parameters allow you to customize the behavior of the action to fit your specific needs. Each parameter's name, description, requirement status, and default value (if applicable) are listed for your reference:

Parameter Name	Description	Default Value
`GITHUB_TOKEN`	`GITHUB_TOKEN` or personal access token. repo and read:org scopes required for personal access token(classic). For scenarios involving data collection from multiple repositories or handling a large number of pull requests, it's recommended to use a personal access token (classic). This parameter is required	-
`GITHUB_OWNER_FOR_ISSUE`	Owner of the repository where an issue with the report needs to be created. This parameter is mandatory if `EXECUTION_OUTCOME` includes `new-issue` or `existing-issue` values.	-
`GITHUB_REPO_FOR_ISSUE`	The repository where an issue with the report needs to be created. This parameter is mandatory if `EXECUTION_OUTCOME` includes `new-issue` or `existing-issue` values.	-
`GITHUB_OWNERS_REPOS`	Repositories to collect data from. Enter values in the format `owner/repo`, separated by commas. Either `GITHUB_OWNERS_REPOS` or `ORGANIZATIONS` must be set. Example: `owner/repo, owner/another-repo`	-
`ORGANIZATIONS`	Organizations from whose repositories data needs to be collected., separated by commas. Repositories from these organizations will be added to the `GITHUB_OWNERS_REPOS` list to create an array with unique repositories. Either `GITHUB_OWNERS_REPOS` or `ORGANIZATIONS` must be set.	-
`SHOW_STATS_TYPES`	Stats types that should be displayed in report. Values must be separated by commas. Can take values: `timeline`, `workload`, `pr-quality`, `code-review-engagement`, `response-time`. Example: `timeline, workload, pr-quality, code-review-engagement, response-time`	`timeline, workload, pr-quality, code-review-engagement, response-time`
`AGGREGATE_VALUE_METHODS`	Aggregate value methods for timelines that should be displayed in report. Values must be separated by commas. Can take values: `percentile`, `average`, `median`. Example: `percentile, average`	`percentile`
`AMOUNT`	The number of closed pull requests to generate the report for. Ignored if `REPORT_DATE_START` or `REPORT_PERIOD` are specified.	`100`
`REVIEW_TIME_INTERVALS`	Enables viewing the percentage distribution among specified values for the time from opening to review, given in hours. Example: `4, 8, 12`	-
`APPROVAL_TIME_INTERVALS`	Enables viewing the percentage distribution among specified values for the time from opening to approve, given in hours. Example: `4, 8, 12`	-
`MERGE_TIME_INTERVALS`	Enables viewing the percentage distribution among specified values for the time from opening to merge, given in hours. Example: `4, 8, 12`	-
`TOP_LIST_AMOUNT`	The number of pull request links to display in the lists for longest-pending reviews, longest-pending approvals, longest-pending merges, the largest and the most commented PRs. Lists will be sorted in descending order, showing the PR title and its value.	`5`
`REPORT_DATE_START`	Sets the start of the period for generating the report. Use the format d/MM/yyyy. The end of the period can be specified with the `REPORT_DATE_END` input. `REPORT_PERIOD` takes precedence over `REPORT_DATE_START`. Example: `20/10/2023`	-
`REPORT_DATE_END`	Sets the end of the period for generating the report. Use the format d/MM/yyyy. The start of the period can be specified with the `REPORT_DATE_START` input. Example: `25/10/2023`	-
`REPORT_PERIOD`	Allows generating a report for a specified time period starting from the action's execution time. If `REPORT_DATE_END` is specified, the period will be limited to this end date. Values format `[unit]:value` separated by commas. Supported units: `years`, `months`, `weeks`, `days`, `hours`, `minutes`, `seconds`. Example: `weeks:2`	-
`PERIOD_SPLIT_UNIT`	Allows for the additional display of reports with data broken down by years, quarters, or months for the reporting period. This extra analysis will be added as comments in the issue. This breakdown can be removed by using the value `none`. Can take values: `years`, `quarters`, `months`, `none`	`months`
`CORE_HOURS_START`	Start of core hours. Excludes non-working hours from the calculations of time-related metrics. By default, a full day is counted. Time should be entered in the format HH:mm. The timezone corresponds to that specified in the `TIMEZONE` input (default is UTC). For correct operation, `CORE_HOURS_END` must also be specified and must be later than `CORE_HOURS_START`. Example: `10:00`	-
`CORE_HOURS_END`	End of core hours. Excludes non-working hours from the calculations of time-related metrics. By default, a full day is counted. Time should be entered in the format HH:mm. The timezone corresponds to that specified in the `TIMEZONE` input (default is UTC). For correct operation, `CORE_HOURS_END` must also be specified and must be later than `CORE_HOURS_START`. Example: `19:00`	-
`HOLIDAYS`	Dates to be excluded from the calculations of time-related metrics. Saturday and Sunday are already excluded by default. Dates should be entered in the format d/MM/yyyy, separated by commas. Example: `01/01/2024, 08/03/2024`	-
`TIMEZONE`	Timezone that will be used in action. Examples: `Europe/Berlin` or `America/New_York`. See the full list of time zones here	`UTC`
`PERCENTILE`	Percentile value for timeline. This parameter is mandatory if `percentile` is specified in the `SHOW_STATS_TYPES` input.	`75`
`ISSUE_TITLE`	Title for the created/updated issue with report	`Pull requests report(d/MM/yyyy HH:mm)`
`LABELS`	Labels for the created/updated issue with report separated by commas. Example: `Report`	-
`ASSIGNEES`	Assignees for the created/updated issue with report separated by commas. Example: `AlexSim93`	-
`USE_CHARTS`	Primarily uses charts and diagrams instead of tables to display data. Set the value to `true` to use charts instead of tables	`false`
`HIDE_USERS`	Hides selected users from reports, while still including their data in the analytics. Use `total` to hide total stats. Users should be separated by commas.	-
`SHOW_USERS`	Displays only specified users in reports, but includes all users in the background analytics. Use `total` to show total stats. Users should be separated by commas.	-
`EXCLUDE_LABELS`	PRs with mentioned labels will be excluded from the report . Values should be separated by commas. Example: `bugfix, enhancement`	-
`INCLUDE_LABELS`	Only PRs with mentioned labels will be included in the report. Values should be separated by commas. Example: `bugfix, enhancement`	-
`EXECUTION_OUTCOME`	This parameter allows you to specify the format in which you wish to receive the report. Options include creating a new issue, updating an existing one, obtaining markdown, or JSON. Markdown and JSON will be available in outputs. Can take mulitple values separated by commas: `new-issue`, `markdown`, `collection`, `existing-issue`. This parameter is required Example: `existing-issue`	`new-issue`
`ISSUE_NUMBER`	Issue number to update. Add `existing-issue` to `EXECUTION_OUTCOME` for updating existing issue. The specified issue must already exist at the time the action is executed. This parameter is mandatory if the `EXECUTION_OUTCOME` input includes `existing-issue` value	-
`ALLOW_ANALYTICS`	Allows sending non-sensitive inputs to mixpanel for better understanding user's needs. Set the value to `false` to disable sending action parameter data	`true`

Use these parameters to tailor the pull-request-analytics-action to your project's specific requirements.

Outputs

Below is a table describing the possible outputs of pull-request-analytics-action:

Output Option	Description
`JSON_COLLECTION`	A string output containing a JSON object with all the data collected by the action. To receive this output, add `collection` to `EXECUTION_OUTCOME`.
`MARKDOWN`	An output containing the report as a markdown string. To receive this output, add `markdown` to `EXECUTION_OUTCOME`.

Recommendations and Tips

Use a Personal Access Token (classic) to generate reports for multiple repositories or to support teams.
Avoid running multiple actions simultaneously that use the same token. This will help prevent hitting secondary rate limits.
Utilize the schedule event for optimal report updates. You can refresh the report every few hours or days to avoid exceeding rate limits and to keep the report up to date. You can find an example configuration here.
To hide individual metrics, specify users in the HIDE_USERS parameter or leave total and GitHub team names in the SHOW_USERS parameter.
To avoid a long list of title changes when updating an existing issue, it is recommended to set the title yourself using the ISSUE_TITLE parameter.
You can filter pull requests using labels with the EXCLUDE_LABELS and INCLUDE_LABELS parameters.

Troubleshooting

If you encounter a Not Found error:

Check the scopes of your personal access token if you're using one.
Verify that you have correctly specified the owner and repository.
Ensure that you have access to the specified repository.
If you're using GITHUB_TOKEN, remember that it only provides access to the repository where the action is running.

You can read more about this in the GitHub documentation.

Privacy and Data Handling

pull-request-analytics-action is stateless; it does not send or store any of the collected data. However, to better understand user needs, fix bugs, and efficiently develop the project, some non-sensitive input parameters are sent to Mixpanel. These data are anonymous and do not provide any information that could identify the project or its data. If you wish to disable parameter data transmission, set ALLOW_ANALYTICS to false.

Usage Limitations

pull-request-analytics-action operates within GitHub's API rate limits and message size constraints, which are generally sufficient for detailed, long-term reporting. However, in rare cases of extremely large datasets, some adjustments might be necessary. For more information, refer to GitHub's documentation on rate limiting. The length of the report generated by pull-request-analytics-action is limited to 65,536 characters due to GitHub Issue size constraints.

How You Can Help

Contributions to pull-request-analytics-action are always welcome, no matter how large or small. Here are some ways you can help:

Star the Project: If you find pull-request-analytics-action useful, consider giving it a star ⭐ on GitHub. This helps increase its visibility and shows support for our work.
Spread the Word: Mention pull-request-analytics-action in your articles, blog posts, and social media. The more people know about it, the better it gets.
Contribute to the Code: Follow our contribution guidelines to make code contributions. Every pull request helps!
Report Bugs: Encountered an issue? Please let us know by opening an issue on GitHub. This is crucial for continuous improvement.
Share Ideas: Have ideas on how to improve pull-request-analytics-action? Open an issue and tell us about your suggestions.

I appreciate any contributions to the project. Your help makes this action better!

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

README.md

README.md

Pull request analytics action

Table of Contents

Motivation

Metrics

Lead Time

Contribution

Discussion Intensity (Author’s Perspective)

Discussion Intensity (Reviewer’s Perspective)

Reviewer Response Time

Metric Trends Over Time

List of Notable PRs

Getting started

Using GitHub Enterprise Server

Configuration Parameters Overview

Outputs

Recommendations and Tips

Troubleshooting

Privacy and Data Handling

Usage Limitations

How You Can Help

Files

README.md

Latest commit

History

README.md

File metadata and controls

Pull request analytics action

Table of Contents

Motivation

Metrics

Lead Time

Contribution

Discussion Intensity (Author’s Perspective)

Discussion Intensity (Reviewer’s Perspective)

Reviewer Response Time

Metric Trends Over Time

List of Notable PRs

Getting started

Using GitHub Enterprise Server

Configuration Parameters Overview

Outputs

Recommendations and Tips

Troubleshooting

Privacy and Data Handling

Usage Limitations

How You Can Help