Conversation
Member
|
Closing stale sync PR. A clean sync will be triggered once the configuration is finalized. |
security-config-sync
Bot
force-pushed
the
security/sync-configs
branch
from
519342e to
b06cbe2
Compare
sutaakar
approved these changes
Mar 6, 2026
This was referenced Mar 6, 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
This PR syncs security scanning configuration files from the central security-config repository, managed by the @opendatahub-io/odh-platform-security team.
Files
semgrep.yaml.gitleaksignore.gitleaks.tomlWhat does this mean for your team?
security-configrepoFor questions or customization requests, open an issue on opendatahub-io/security-config.