EN

Canada (EN)

Australia (EN)

Canada (FR)

France (FR)

Ireland (EN)

United Kingdom (EN)

United States (EN)

View all recipes

GitHub pull request trends report

Report on and spot trends over time across the number of pull requests that have been merged.

How to track the volume of GitHub pull requests over time

With Rippling’s “Pull Request Trends Report,” you can report on and spot trends over time across the pull requests merged across your team or department.

What do you need?

Rippling HRIS

Rippling App Management

GitHub

Use Recipe Template

Recipe Overview

Being able to ship quality code, and do it fast, is essential for SaaS companies to stay competitive in a tough market.

That’s why it’s important for engineering leaders to keep an eye on the speed at which their team is shipping code so they can spot when their teams are being less productive than average, and be able to investigate and take quick action should that happen.

With this Recipe, you’ll be able to pull data from GitHub to view the total number of PRs that have been merged across the department, as well as by employee, team, manager and more.

You’ll also be able to normalize this report by the size of a team, to understand the average number of PRs being merged per employee over time. That way, it’s easy to stay on top of overall velocity, and spot trends over time that they can use to increase productivity in the long run.

Want to view your numbers over a 60-day period instead? As with all our report Recipes, you can customize this template with additional data, filters, grouping and more to help you answer your specific questions

Functions that use this recipe

Companies that use this recipe

Similar Recipes