You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 9, 2024. It is now read-only.
By default semgrep-action scans only the diff added in the PR. That's very neat optimization and it probably should stay that way by default.
However for the projects just adopting semgrep CI integration it would be great to be able to explicitly configure full source code scan for CI running on PR.
Right now it's possible by changing trigger event to "push" instead of "pull_request" and switching scan policy to blocking mode but that's far from obvious for newcomers.
Having explicit variable (similar to 'auditOn' for example) to select between full and partial scans (defaulting to partial to preserve the current behavior) would be great to streamline initial integration.
The text was updated successfully, but these errors were encountered:
By default semgrep-action scans only the diff added in the PR. That's very neat optimization and it probably should stay that way by default.
However for the projects just adopting semgrep CI integration it would be great to be able to explicitly configure full source code scan for CI running on PR.
Right now it's possible by changing trigger event to "push" instead of "pull_request" and switching scan policy to blocking mode but that's far from obvious for newcomers.
Having explicit variable (similar to 'auditOn' for example) to select between full and partial scans (defaulting to partial to preserve the current behavior) would be great to streamline initial integration.
The text was updated successfully, but these errors were encountered: