📖
Typo Help Docs
  • Welcome
  • Getting Started
    • Onboarding
    • Integrations
      • Git
        • GitHub
        • GitLab
        • BitBucket
        • Azure Repos
        • Gitlab On-prem
      • Issue Tracker
        • JIRA
        • Linear
        • GitHub Issue
        • Shortcut
        • ClickUp
      • CI/CD Tool
        • Circle CI
        • Jenkins
        • Heroku
        • GitHub Actions
        • Azure DevOps
        • Custom Deployment Webhook
      • Slack
    • How Requestly setup Typo in a few days
  • Platform
    • Dev Analytics
      • DORA
      • Insights
        • Teams
        • Members
        • Sprints
        • Pull Requests
        • Deployments
      • Incident
      • Goals
      • Investment
      • Initiative
      • WorkLog
      • Custom Reports
      • Settings
        • Teams
        • Member
        • Repository
        • Projects
        • Manage Access
        • Notifications
    • Code Health
      • Code Review
      • Code Coverage
    • DevEx
  • Implementation Plan
    • Phase 1 - Setting Up Data Sources
    • Phase 2 - Metric Configuration
      • Dev360
      • Code Health
      • DevEx
    • Phase 3 - Team Rollout
  • Engineering Metrics
    • DORA
      • Cycle Time
      • Deployment PRs
      • Change Failure Rate
      • Mean Time to Restore
    • Pull Request Metrics
      • Avg. Commits During PR Review
      • Coding Days
      • Coding Time
      • Merge frequency
      • Merge Time
      • Pickup Time
      • PR Size
      • PRs Merged without Review
      • Review Time
      • Efficiency Score
    • Sprint Metrics
      • Carry over
      • Developer Workload
      • Issue Cycle Time
      • Issues At-Risk
      • Scope creep
      • Team Velocity
      • Work Breakup
      • Work Progress
    • Code Quality Metrics
      • OWASP Top 10
      • Vulnerability
      • Security
      • Performance
      • Duplication
      • Code Smell
    • Deployment Metrics
      • Deployment - Failure
      • Deployment - Frequency
      • Time to Build
    • Incident Metrics
      • Incident - Opened
      • Avg Resolution Time
    • DevEx Metrics
      • DevEx Score
      • Space mood
      • Response Rate
      • Manager Support
      • Developer Flow
      • Product Management
      • Development & Releases
      • Culture & Values
  • Configurations
    • Cycle Time
    • Deployment PRs
    • Change Failure Rate (CFR)
    • Mean Time To Restore (MTTR)
    • CI/CD - Deployment
    • Incident
    • Initiative
    • Investment Distribution
    • PR Labels
    • Code Health
    • Code Coverage
    • DevEx
    • Notifications
    • Manage Access
  • FAQ's
    • Data Security
      • GitHub App Permissions Details
      • Why does Typo need write permission to my code?
      • Does Typo has access to my code?
      • What data security guidelines does Typo follow?
    • Integrations
      • Can I connect multiple Git organizations to get a consolidated view on Typo?
      • Can Typo application work with on-prem Gitlab?
      • How do I unlink the JIRA tracker & integrate Linear?
      • How do I change a CI/CD integration?
      • How do I export my Git data?
      • Can I integrate with Azure Repos?
    • Pricing
      • How does the free plan work and how can I switch to it?
      • How does the pricing work?
      • How do I upgrade my plan?
      • How are active users Counted for billing?
    • Access Management
      • My team member is not able to login to Typo
    • Metrics
      • How does Typo predict developer burnout?
      • Is there a way to change the branch that Deployment PRs are measured against?
      • Synchronize “CFR” & “MTTR” without incident management?
      • How quick does the pull-request page update? I closed a PR but the Typo still shows Awaiting Review
      • How do I add any new repo?
      • How to put checks before merging a PR in BitBucket
      • How to Configure Typo Code Health Checks to Block a PR Merge in Git
      • Can I exclude a person from metrics calculation?
      • Can I track the Cycle time based on the status of the JIRA tickets?
      • How to exclude a PR from any metric calculation?
      • My data is not visible, I have synced the repo
      • How do I create and download a custom report?
    • Platform
      • Which programming languages are supported for code coverage feature?
      • How do I manage notifications?
      • Can I use your application on-premise?
    • Delete Account
      • How can I delete my account?
Powered by GitBook
On this page
  1. Engineering Metrics
  2. Pull Request Metrics

PRs Merged without Review

PreviousPR SizeNextReview Time

Last updated 9 months ago

Pull Request merged without review refers to all those pull requests that are merged without the review being approved.

For all the merged PRs, Typo considers the ones that do not have any ‘Approved’ status associated with them. In case of merged PRs having review comments but not approval, such Pull Requests are also considered as merged without review.

Benchmarking PRs merged without review helps engineering teams identify potential gaps in their code review processes and ensure code quality standards are upheld. By tracking this metric, teams can quantify the extent of unreviewed code changes, which may lead to increased technical debt, bugs, and regressions.

How does measuring Pull Request merged without review help in improving the Engineering teams' efficiency?

  1. Maintaining Code Quality: Monitoring PRs merged without review helps ensure that all code changes are scrutinized before integration. By reducing the number of PRs merged without review, teams can maintain higher standards of code quality and reduce the likelihood of introducing bugs or errors into the codebase.

  2. Promoting Collaboration: Encouraging the review process fosters collaboration among team members. Reviewing PRs by peers provides an opportunity for knowledge sharing, feedback, and constructive discussions. This collaborative environment ultimately leads to better solutions, increased code understanding, and improved team cohesion.

  3. Mitigating Risks: Unreviewed PRs pose risks to the stability and reliability of the software. By measuring and minimizing the occurrence of PRs merged without review, teams can mitigate these risks and enhance the overall robustness of the codebase. This proactive approach helps prevent potential issues from impacting users and ensures smoother project delivery.

  4. Enhancing Accountability: Implementing a review process ensures that all code changes are accountable to team members. By measuring PRs merged without review, teams can identify any lapses in accountability and address them accordingly. This promotes a culture of responsibility and transparency within the team, leading to better governance and project management.

  5. Continuous Improvement: Regularly tracking PRs merged without review allows teams to evaluate their review processes and identify areas for improvement. By analyzing trends and patterns, teams can implement strategies to streamline the review process, address bottlenecks, and optimize workflow efficiency. This continuous improvement cycle fosters a culture of learning and adaptation, driving long-term productivity and success.