Collecting Semgrep GitHub Actions logs from GitHub
Collect logs from GitHub Actions to troubleshoot Semgrep CI scans.
15 docs tagged with "Semgrep in CI"
View all tagsConfigure GitHub Actions to use the nonroot Semgrep docker image
How to properly configure your GitHub Actions workflow to use the `nonroot` Semgrep docker image
Does Semgrep scan compressed files or other non-code files?
Options to scan compressed files or other artifacts with Semgrep.
Failed to run a git command during a pull request or merge request scan
When running Semgrep in CI with a pull request or merge request as the triggering event, Semgrep runs some additional git commands to determine the behavior for the scan. The scan exits with an error if these commands fail. A message like the following shows in the output:
GitLab "Job's log exceeded limit" error
Collect verbose logs from GitLab to troubleshoot Semgrep CI scans.
How to run different versions of Semgrep
How to test scans with different versions of Semgrep.
Receive Semgrep MR comments through a GitLab runner
Set additional environment variables to receive Semgrep MR comments through a GitLab runner.
Scanning a monorepo in parts
How to scan a monorepo in parts for better CI performance and clearer findings organization
Semgrep in CI vs CLI: align your SAST scan results and understand differences
How to align your scan results between CI and CLI and understand differences in behavior.
Set up reusable GitHub workflows for Semgrep scans
Learn how to set up reusable GitHub workflows for Semgrep scans.
Why are duplicate findings appearing after running Semgrep in CI?
To prevent duplicated findings, perform full scans only on the main branch of your repository.
Why are there new source code manager (SCM) connections that I didn't manually configure listed in Semgrep AppSec Platform?
Learn why there are new SCMs listed in Semgrep AppSec Platform.
Why aren't findings populating in the GitHub Advanced Security Dashboard after running Semgrep in CI?
To prevent "resource not accessible by integration" error when running job to upload findings to GitHub's Advanced Security Dashboard
Why did the comments on a PR or MR not appear inline?
When Semgrep comments on PR or MR findings, the comments are usually posted on the line of code where the finding is identified (inline). However, there are two common reasons why comments may not appear inline.
Why is my repository not receiving PR or MR comments?
Use this reference to check why you may not be receiving Semgrep comments on PRs or MRs.