- How deep: a thorough deep scan, or a fast PR scan of just the diff.
- How many repos: a single repository, or several at once (multi-repo).
Deep scans vs PR scans
This is the core distinction. A deep scan analyzes everything; a PR scan analyzes only what changed.A PR scan classifies each finding as new, persisting, or fixed
relative to the branch, so reviewers see exactly what the change introduces.
See PR checks.
Single-repo and multi-repo
Scope is a property of a deep scan: it can cover one repository or several in a single run.Single-repo
A deep scan of one repository. The common case for most workflows.
Multi-repo
One deep scan across several repositories at once, ideal for a service split
across repos, or a portfolio you want to assess together. Findings roll up
across every repo the scan touched.
Scheduled scans
A scheduled scan is just a deep scan on a recurring cadence (and it can be multi-repo). Each run updates the repository’s baseline commit, which is how Gecko tells genuinely new issues apart from pre-existing ones. See Scheduled scans.Fix recheck
A lightweight re-evaluation of previously open findings to confirm whether each is now gone. It’s how Gecko marks a finding Fix verified after a merge. It doesn’t run the full pipeline. See Auto-fix PRs.Where scans live
- Repository → Scans tab: every scan for one repository, filtered by all / PR / scheduled.
- Scans (top-level): all scans across the team.
- Scan detail: the full findings table for one scan, plus its wiki and endpoints. Multi-repo scans show every repository they covered.