Pull Request Checks
Introduction to automated security scans with PR Checks
The Snyk PR Checks feature allows developers to auto-scan their PRs for issues before merging their code. As Snyk acts as an automated pseudo-team member (an “expert security reviewer”), it finds potential issues, leaving review notes on your PR before the code is committed.
While PRs are the points in the development process where code reviews happen, PR Checks allow security scanning to be integrated with developer workflows, empowering dev teams and helping to prevent security issues from occurring in deployed code.
Test the change
The Snyk PR Checks feature allows you to test a change to the current codebase to see if that change introduces a problem. This change testing makes it easier to maintain the security of your codebase on an ongoing basis.
For developers, change-related flaws are relevant and easy to fix, and fixing change-related flaws rather than accumulated flaws makes rolling out secure code easier. You can detect security issues early in the development process, see the test results immediately after you write new code, and find and fix issues as they emerge, all in your native workflow.
Testing “before” and “after”
The Snyk PR Checks feature runs live tests of the “before and after” branch with the PR and fails only if the new branch has more issues. This allows you to address problems that have been introduced since the last scan, for example, new vulnerabilities introduced externally. Snyk PR Checks are triggered by a change in your code, and find issues across the entire repository. Thus, a PR check finds issues in your code as well as other issues introduced since the last Snyk scan.Use the Snyk PR Checks feature to prevent new security issues from entering your codebase by automatically scanning code changes in real time as soon as you submit a pull request (PR) in your source code manager (SCM).
Why use PR Checks
| Benefits | Details |
|---|---|
Automatically scanned pull request | Scan code changes in real-time as soon as a pull request is submitted, to catch potential issues before they go into production. |
Results displayed in your source code manager | Make use of security reviews and notes left by Snyk on your pull requests. |
Code change testing for security issues | Test changes to your codebase for any security issues, ensuring that your code stays secure over time. |
Branch testing | Test branches before and after implementing changes to fail only if the new branch has introduced issues. Prevent merging pull requests with failed security issues. Note that Snyk monitors all pull requests made to the monitored repository. |
What to test for
You can analyze PR Checks results in your SCM to test for dependency and licensing issues using Snyk Open Source and code security using Snyk Code.
How PR checks work
The following diagram explains how Snyk Checks PRs in your development workflow.
PR checks proceed as follows:
A developer creates a pull request (PR) in an SCM integrated with Snyk.
A webhook is triggered from the SCM to Snyk
Snyk automatically scans the code changes in the PR for issues.
Snyk leaves security reviews and notes on the PR.
The developer can view the PR Checks results and fix identified issues before merging the code.
The PR Checks results appear as Passed or Failed directly in the SCM, preventing PRs from being merged with security issues.
For more information on working with PR Checks, see the following pages:
Last updated
