Skip to main content

    How to trigger diff-aware scans

    When working with a CI provider, you can set Semgrep to run diff-aware scans as well as full scans. Diff-aware scans run on your code before and after some baseline, and only report findings newly introduced in the commits after that baseline.

    Include the following definition in your GitHub Actions configuration file to enable diff-aware scanning:

    on:
    # Scan changed files in PRs (diff-aware scanning):
    pull_request: {}

    Example

    # Name of this GitHub Actions workflow.
    name: Semgrep

    on:
    # Scan changed files in PRs (diff-aware scanning):
    pull_request: {}

    jobs:
    semgrep:
    # User definable name of this GitHub Actions job.
    name: semgrep/ci
    # If you are self-hosting, change the following `runs-on` value:
    runs-on: ubuntu-latest

    container:
    # A Docker image with Semgrep installed. Do not change this.
    image: semgrep/semgrep

    # Skip any PR created by dependabot to avoid permission issues:
    if: (github.actor != 'dependabot[bot]')

    steps:
    # Fetch project source with GitHub Actions Checkout. Use either v3 or v4.
    - uses: actions/checkout@v4
    # Run the "semgrep ci" command on the command line of the docker image.
    - run: semgrep ci
    env:
    # Connect to Semgrep AppSec Platform through your SEMGREP_APP_TOKEN.
    # Generate a token from Semgrep AppSec Platform > Settings
    # and add it to your GitHub secrets.
    SEMGREP_APP_TOKEN: ${{ secrets.SEMGREP_APP_TOKEN }}

    Not finding what you need in this doc? Ask questions in our Community Slack group, or see Support for other ways to get help.