Uh oh!
There was an error while loading. Please reload this page.
chore: add redacted gitleaks history baseline - #436
Merged
Conversation
Records a redacted gitleaks baseline at the repo root so the full-history dispatch scan runs clean, and wires the code-quality caller to consume it via the gitleaks-baseline input. Part of tracebloc/backend#1303. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
LukasWodka
commented
Jul 30, 2026
ContributorAuthor
bugbot run |
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit 9ae46eb. Configure here.
shujaatTracebloc
approved these changes
Jul 31, 2026
shujaatTracebloc
left a comment
Contributor
There was a problem hiding this comment.
Reviewed against the checklist:
- Baseline redaction: every
SecretisREDACTEDwith aFingerprintpresent; no cleartext values (leftover text inMatchis only key names / assignment context). - Diff scope: only
.gitleaks-baseline.json+ the caller wiring;soft-fail: falseretained, so the gate stays armed and only new secrets fail it. quality / gitleaksis green, confirming the baseline suppresses correctly.
LGTM 👍
LukasWodka
commented
Aug 2, 2026
ContributorAuthor
/fr-pass |
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 freeto 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.
Adds a redacted gitleaks history baseline so the full-history dispatch scan runs clean; 1 historical finding triaged, classification relayed privately. Part of tracebloc/backend#1303
🤖 Generated with Claude Code
Note
Low Risk
CI configuration and a baseline allowlist only; no runtime, auth, or application logic changes.
Overview
Adds
.gitleaks-baseline.jsonwith one redacted, triaged historical hit (generic-api-keyon anIdempotencyKeystring ininternal/submit/submit_test.go) so gitleaks can treat it as already reviewed instead of failing the gate.The code quality reusable workflow caller now passes
gitleaks-baseline: .gitleaks-baseline.json, so manual whole-repo / full-history scans can run clean under the armedsoft-fail: falsepolicy (backend#1303).Reviewed by Cursor Bugbot for commit 9ae46eb. Bugbot is set up for automated code reviews on this repo. Configure here.