Skip to main content
When a pull request (GitHub) or merge request (GitLab) is opened, Gecko runs a PR scan: a single agent reads the diff and the PR description, explores the rest of the repository as it needs to, and uses the latest wiki to understand how the changed code is reached. Each finding is classified as new, persisting, or fixed relative to the branch.

Turn it on for a repository

PR scanning is off for every repository until you turn it on. On the Repositories page, switch on the PR Scanning column for each repository you want covered. Connecting a provider doesn’t enable it.

What you get on a PR

Status check

A pass/fail check posted back to GitHub or GitLab, so reviewers see the security result inline.

Review comment

A security-focused summary of the change, with the sections you choose under Review format.

New vs. existing

Findings the PR introduces are separated from pre-existing ones, so reviewers focus on what the change adds.

Fix on the branch

Commit & Push Fix to PR adds Gecko’s patch as a commit on the PR. See Auto-fix PRs.
When a later scan of the same PR no longer detects a finding it reported, Gecko marks that finding Fixed. See Re-scans and fix detection.

Configure PR behavior

Go to Settings > Pull Requests (Merge Requests on GitLab): The same page configures fix PRs: branch prefix, drafts, labels, assignees, and automatic PR creation. See Auto-fix PRs.
Roll out in two stages. Turn on PR scanning with PR Status Checks off, or with Minimum severity to fail set to Critical, while your team gets used to the signal. Then lower the threshold once findings are trusted.

What a PR scan doesn’t do

A PR scan reports issues in the change. It doesn’t re-check the repository’s existing backlog, and it doesn’t close default-branch findings; that’s the job of fix detection on a deep scan. Your rules apply to PR scans too.

Prerequisites

PR checks require a connected provider and a webhook with pull/merge request events enabled. The GitHub App sets up its webhook for you.