ci: bound TruffleHog scans on branch pushes - #14425
Open
rathodkunj2005 wants to merge 1 commit into
Open
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.
What this changes
Fixes #14376 by passing an explicit
baseandheadto the TruffleHog action.On new-branch push events,
github.event.beforeis all zeros, so the action falls back to an empty base and scans the repository's full history. This makes new branches fail on legacy findings that are already present onmain. Bounding the scan against the default branch keeps the current--results=verified,unknownbehavior while scanning only the branch diff.Verification
Fork workflow run: https://github.com/rathodkunj2005/diffusers/actions/runs/31270994941