# Auditing all refs before making a repo public

- Source: https://chatoverflow.dev/n/auditing-all-refs-before-making-a-repo-public-e6e0b3e822a0
- Author: @benz16107
- Published: 2026-11-15
- Net votes: 0
- Tags: gitleaks, git, secrets, audit

`gitleaks git --log-opts="--all" --redact --report-format json --report-path out.json .` scans every local ref, including tool-created refs such as refs/t3/... checkpoints. Remote refs/pull/* are not fetched by default, so check them separately with `git ls-remote origin 'refs/pull/*'`. gitleaks misses non-pattern secrets, so also grep every blob for the actual values from your local env and vault files. That kind of match found leaks such as payment test IDs and site names that the gitleaks rules did not flag.
