Repository navigation
Narrow gitleaks allowlist to fixture values; harden the allowlist guard - #2351
Closed
remigiusz-antczak wants to merge 1 commit into
Closed
remigiusz-antczak wants to merge 1 commit into
remigiusz-antczak wants to merge 1 commit into
Conversation
…y hits .gitleaks.toml exempts only the fictional fixture values in the two secret test scripts instead of whole files; its comment states the value regexes apply repo-wide. .gitleaksignore lists the fingerprints of the 19 remaining history hits, all triaged as fictional, so a history scan reports 0 findings. test_gitleaks_allowlist.sh asserts the 0-finding history scan (skipped on shallow checkouts), counts a probe as detected only on exit 1 plus an aws-access-token report (any other exit fails), and fails when gitleaks is missing under CI or REQUIRE_GITLEAKS=1. Tests: test_gitleaks_allowlist 1/1 (rc 0); gitleaks history scan 0 findings Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Collaborator
Author
|
Superseded by a combined single-commit PR that also fixes the per-PR leg failure. |
remigiusz-antczak
added a commit
that referenced
this pull request
Nov 13, 2026
.gitleaks.toml exempts only the fictional fixture values in the two secret test scripts instead of whole files; its comment states the value regexes apply repo-wide. .gitleaksignore lists the fingerprints of the 19 remaining history hits, all triaged as fictional, so a history scan reports 0 findings. test_gitleaks_allowlist.sh asserts the 0-finding history scan (skipped on shallow checkouts), counts a probe as detected only on exit 1 plus an aws-access-token report (any other exit fails), and fails when gitleaks is missing under REQUIRE_GITLEAKS=1. Add a gitleaks job to ci.yml: full-history checkout without persisted credentials, gitleaks 8.30.1 installed from its release tarball and verified against a hardcoded sha256, then REQUIRE_GITLEAKS=1 bash scripts/test_gitleaks_allowlist.sh. The gates aggregate needs it; job permissions stay contents: read. The guard is strict (missing gitleaks, shallow history or no .git FAILs) only when REQUIRE_GITLEAKS=1 is set. Keying strictness on CI broke the per-PR test legs, which run every test script with CI set but do not install gitleaks; they now SKIP it. Supersedes #2351 and #2352. Tests: 3/3 test_gitleaks_allowlist.sh runs (PASS with gitleaks; SKIP with CI=1 and no gitleaks; FAIL with REQUIRE_GITLEAKS=1 and no gitleaks). actionlint clean; size gate ok. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Supersedes #2341. Its base (#2338) was squash-merged, so the stacked branch conflicted. This is the same change as one commit on current main.
Tests: test_gitleaks_allowlist.sh PASS.
🤖 Generated with Claude Code