PR Checks
Use Snyk PR Checks 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
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. Prevention of merging pull requests with failed security issues.
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.
Step-by-step process
A developer creates a pull request (PR) in an SCM integrated with 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.
What's next?
Last updated
Was this helpful?