Repository navigation
sec: regenerate .secrets.baseline to clear detect-secrets CI failure - #424
Merged
Merged
Conversation
Contributor
Preview EnvironmentA preview environment can be spun up on demand for this PR.
|
github-actions
Bot
added
area: root
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
… a redacted baseline file
github-actions
Bot
added
github_actions
…s-baseline-3 # Conflicts: # .gitleaks-baseline.json # .secrets.baseline
akshitpatel1732
approved these changes
Sep 16, 2026
akshitpatel1732
left a comment
akshitpatel1732
left a comment
Contributor
There was a problem hiding this comment.
Thanks @raaidrushdy for fixing the failing workflow.
github-actions
Bot
removed
the
needs-triage
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
3 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
Regenerates
.secrets.baselineto audit one new finding, clearing thedetect-secretsCI check that's been failing onmainsince #420 was merged.Type of Change
Affected Components
(This PR touches only
.secrets.baselineat the repo root.)Motivation
The new CI-enforced
detect-secretscheck (#420) has been failing on every push tomainsince the merge because of one unaudited finding: an example password insecurity/reports/README_report_service.mddocumentation (not a real secret).Testing Done
Ran
detect-secrets scan --baseline .secrets.baseline, which surfaced the one new finding. Audited it withdetect-secrets audit .secrets.baselineand confirmed it's a documentation example password, not a real secret, markedis_secret: false. Verified withdetect-secrets audit .secrets.baselinereporting "Nothing to audit!" and confirmed the file is valid JSON.Security Considerations
No new security exposure; this only updates metadata used by a secret-scanning tool.
Breaking Changes
Rollback Plan
Checklist
Screenshots
N/A - no UI impact.