PR Impact FAQs

Question 1

Can PR Impact be integrated into a CI/CD pipeline?

Accepted Answer

Absolutely. PR Impact is CI-friendly, offering configurable exit codes for its `breaking` and `risk` commands. This allows you to set up automated quality gates in your pipelines, preventing high-risk or breaking changes from being merged.

Question 2

How does PR Impact detect breaking changes?

Accepted Answer

PR Impact identifies removed exports, changed function signatures, altered types, and renamed exports within your codebase. It then maps these changes to their downstream consumers, providing early warnings about potential breaking issues.

Question 3

What is PR Impact?

Accepted Answer

PR Impact is a static analysis tool designed for pull requests. It automatically detects breaking API changes, maps the 'blast radius' of code changes, flags test coverage gaps, and calculates a comprehensive risk score to ensure safer merges.

Question 4

What is the 'Impact Graph' feature?

Accepted Answer

The Impact Graph visualizes the direct and indirect effects of code changes. By building an import-dependency graph, it shows which files are directly modified and which others are indirectly affected, revealing the full 'blast radius' of a pull request.

Question 5

What factors contribute to PR Impact's weighted risk score?

Accepted Answer

The tool calculates a 0-100 risk score based on six key factors: breaking changes detected, untested code, diff size, documentation staleness, configuration changes, and the breadth of impact. This provides a holistic assessment of PR risk.

PR Impact

PR Impact

Key Features

Use Cases

Key Features

Use Cases