See what's new on Keypup!  📢

PR Compliance Report

Get a report of all your merged PRs with their build and approval status for Audit and Compliance purposes.

Use PR Compliance Feed

Track the Build and Approval of all Merged Pull Requests (PRs) in Real Time

with the

PR Compliance Report

Get a report of all your merged PRs with their build and approval status for Audit and Compliance purposes.

Use PR Compliance Feed
PR Compliance ReportPR Compliance ReportPR Compliance Report

From startups to large enterprises, Keypup serves all the unique complexities related to project size, structure and teams, including:

“Keypup has been instrumental in helping us gain a better perspective on our engineering activities and identifying bottlenecks. Its ease of use combined with its comprehensive features made a difference for us”

Bruno D'Auria

Engineering Director

“Great product with great support!

Keypup is extremely flexible in its reporting. Once you get your raw data connected, there is almost nothing it can't do. There is a wealth of tables, charts and other reports available. As Director of a software development team, I use Keypup to report on our work efficiencies to senior managment. Keypup makes this task very simple to produce each week.”

Brad B.

Director, Software Development

Understand the PR Compliance Feed Report

The PR compliance report provides a list of merged PRs in a given period alongside their build and approval status. In addition, a PR’s complexity is provided, based on the number of lines changed, to quickly evaluate the impact of non-compliant pull requests:

  • 0 to 250 lines: Low complexity (➖)
  • 251 to 1000: Medium complexity (➕)
  • 1001 and above: High complexity (➕➕)

This report is particularly handy to isolate exceptions or uncover poor habits among the team.

Facilitate Software Audits with the PR Compliance Feed Report Template 

We recommend you adopt the following procedure as soon as possible in order to facilitate audit and compliance efforts such as SOC 2:

  • Make sure that builds are properly run, prevent engineers from merging their own code, and promote peer reviews.
  • By defining a minimum number of reviews in GitHub, GitLab or Bitbucket, you can streamline review thresholds directly on your tools.
  • GitHub, GitLab and Bitbucket administrators should leave a comprehensive comment on the pull request that explains the reason for merging without approval.
Use PR Compliance Feed