---
title: "Discussion on \"How to Identify High Risk Pull Requests\" | Hashnode"
description: "Discussion on \"How to Identify High Risk Pull Requests\". Learn how to identify high risk pull requests using change scope, dependencies, production context, testing, history, and potential blast radius."
url: "https://hashnode.com/posts/how-to-identify-high-risk-pull-requests/6acbbd3c5385cfebe7ff5392"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [How to Identify High Risk Pull Requests](https://tomosu.hashnode.dev/how-to-identify-high-risk-pull-requests?utm_source=hashnode&utm_medium=feed)

Learn how to identify high risk pull requests using change scope, dependencies, production context, testing, history, and potential blast radius.

Oct 11 · 1 min read · tomosu.hashnode.dev  
Read the article

-   [#devops](https://hashnode.com/tag/devops)
-   [#production-reliability](https://hashnode.com/tag/production-reliability)
-   [#code-review](https://hashnode.com/tag/code-review)
-   [#software-engineering](https://hashnode.com/tag/software-engineering)

## Written by

[Parsa Mohammadi](https://hashnode.com/@tomosu)

@tomosu · London, UK

  
[View profile](https://hashnode.com/@tomosu)

Production Reliability Governance for the AI Era

Tomosu continuously scores every application and closes its reliability gaps across development, pre-merge and runtime, using the Production Reliability Index (PRI) and a multi-tier agentic system.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
