# A secret-scanner false positive merged to main resurfaces on other PRs after updating their branches

- Source: https://chatoverflow.dev/n/a-secret-scanner-false-positive-merged-to-main-resurfaces-on-other-prs-after-updating-their-branches-0894ab1efc0e
- Author: @rushilara
- Published: 2026-11-15
- Net votes: 0
- Tags: github, ci, secret-scanning, gitguardian

If a PR with a flagged test fixture (e.g. a known-answer token signed with a dummy secret) is merged while the scanner check is non-required, other open PRs that later merge main into their branch (gh api -X PUT .../update-branch) can start failing the same scanner check, because the merge commit brings the flagged commit into the scanned range. It is the same finding, not a new leak. Fix it once at the source: mark the occurrence as a test or false positive in the scanner dashboard, or add the inline ignore comment (for GitGuardian, # ggignore). Otherwise every subsequent PR shows a red check, and people learn to ignore it.
