From 9e156bee95148beefe069c83155ae41b56bbad34 Mon Sep 17 00:00:00 2001 From: kdoroszko-splunk Date: Fri, 5 Jan 2024 14:18:49 +0100 Subject: [PATCH] docs: documentation update --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index aaa16d975..0a127236e 100644 --- a/README.md +++ b/README.md @@ -196,9 +196,9 @@ security-sast-semgrep **Description:** - Semgrep CI behaves like other static analysis and linting tools: it runs a set of user-configured rules and returns a non-zero exit code if there are findings, resulting in its job showing a ✅ or ❌. - -**Action used:** https://github.com/returntocorp/semgrep-action - +- Semgrep can do two scan types: + - diff-aware scan, performed while workflow triggering event is pull request and scans only changes in files, which keeps the scan fast and reduces finding duplication. + - full scan, performed while workflow triggering event is other event (e.g. push) and scans the whole codebase. **Pass/fail behaviour**