fix: allowlist mock workload access token in gitleaks config#47
Merged
scottschreckengaust merged 1 commit intomainfrom Apr 23, 2026
Merged
fix: allowlist mock workload access token in gitleaks config#47scottschreckengaust merged 1 commit intomainfrom
scottschreckengaust merged 1 commit intomainfrom
Conversation
The context-hydration test uses `wat-opaque-123` as a mock workload access token. Gitleaks flags this as a generic-api-key false positive across all commits. Add a path-scoped allowlist entry to suppress it. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
scottschreckengaust
force-pushed
the
fix/gitleaks-baseline
branch
from
5104b7a to
f769ea8
Compare
krokoko
approved these changes
Apr 23, 2026
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
2 participants
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.
Summary
context-hydration.test.tsto suppress false positive on mock workload access token (wat-opaque-123)generic-api-keyrule flags this test fixture value across all git history, blocking everygit pushvia the pre-push security hookContext
The mock token was introduced in commit
d402a681and triggers gitleaks on every push, even though it is not a real credential. The existing.gitleaks.tomlalready has a similar allowlist for PEM fixtures in agent tests — this follows the same pattern.Test plan
gitleaks detect --source . --no-bannerreportsno leaks foundafter the changesecurity:secretsstage passes🤖 Generated with Claude Code