Consistent Ignores for Snyk Code Pull Request Checks

Pull Request Check default ignore behavior

When viewing a pull request (PR) check from Snyk in your integrated SCM, ignored findings do not contribute to the PR check outcome. A PR check will not fail due to an ignored finding. Additionally, the Snyk PR experience will include the count of active (unignored) findings in the summary comment and display each finding as an inline comment within the PR.

If a finding is ignored after a PR check has already been completed, the PR check must be retriggered by committing again to the PR. Upon retriggering, the PR check the following changes will occur:

• The ignored finding will no longer be counted in the summary table.

• The inline comment for the ignored finding will be collapsed by default and marked as resolved.

Ignores are respected in Snyk Code Pull Request Checks regardless of whether they are created through policy or for an individual snyk/assets/finding/v1 value.

Example: Snyk Pull Request Check with ignored finding

The following example shows the behavior of a Snyk Code issue in a Pull Request (PR) Check in GitHub before and after it is ignored.

In the following screenshots, a high-severity issue was detected, causing the Snyk PR Check to fail.

You can see all findings, including ignored ones, by selecting View Details from the PR page of your SCM integration.

Before being ignored, the finding appears as an inline comment in your SCM integration.

After an ignore is applied, and a PR check is re-triggered, the inline comment for the ignored finding is collapsed by default and marked as resolved.