Repository navigation
fix(ci): retain gitleaks findings for fourteen days - #6
Merged
Merged
Conversation
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.
The shared secret-scanning workflow retains
gitleaks-findingsfor 30 days. Platform and pipelines inherit that retention through their immutable workflow pins, so their repository workflow retention caps do not cover these reports.Reduce the shared upload retention to 14 days. Scanning rules, redaction, failure handling and run-log retention stay unchanged. Consumer pins will be updated separately after a person lands this PR.
Refs https://github.com/60xAI/ai-brain-platform/issues/4451 and https://linear.app/60x/issue/DEV-2875.
Verification
Risk and rollback
Open in [code]smith · Need help on this PR? Tag
@codesmith-botwith what you need.Summary by CodeRabbit