Two fix paths
Fix PR on the scanned branch
For findings from a deep scan, click Create PR (Create MR on
GitLab). Gecko opens a branch (default prefix
gecko/) with the patch
applied and raises a pull or merge request for review.Commit to an existing PR
For findings from a PR scan, click
Commit & Push Fix to PR. Gecko commits the fix to the PR’s head branch
so it rides along with the change.
Open a fix PR
1
Open the finding's Fix tab
Review the proposed patch in the finding drawer.
2
Create the PR
Click Create PR. Gecko creates the branch and PR, with the change
attributed to Gecko, and the finding moves to In Progress.
3
Review and merge
Treat it like any other PR: review the diff, run CI, and merge when you’re
satisfied. Merging marks the finding Fixed immediately. Closing the PR
without merging sets the finding back to Open.
Patch status
The finding’s patch shows where the fix is: generated (proposed), applied (a PR or commit exists), or merged.Pull request settings
Configure fix PRs in Settings > Pull Requests:
When Auto-create Pull Requests is on, two more options narrow what it
opens PRs for:
- Severity threshold: skip findings below this severity. Defaults to High.
- Finding types: only open PRs for these vulnerability types. Leave it empty for all types.
A merged fix PR closes the finding Gecko opened it for. To have Gecko
confirm fixes you write yourself, see
Fix a finding and confirm it’s gone.