Repository navigation
Conversation
Public repos cannot call private m0-pipelines. Use the public gitleaks/gitleaks-action that other orgs already run.
The previous commit stored the expressions as literal text, so the scan never received GITHUB_TOKEN or GITLEAKS_LICENSE.
The stock action misses deployer_pk-style keys. Fetch the shared baseline so a 32-byte hex is caught regardless of the variable name.
Call the pinned secret-scan workflow so EVM rules apply and every commit in the repo is scanned, not only the pull request diff.
Vault pointers are not secrets. The key is injected by the op CLI at runtime.
False-positive rules can change in one place while these callers stay put.
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.
Summary
gitleaks/gitleaks-actionv3.0.0 on pull requests, pushes tomain, and a monthly schedule.GITLEAKS_LICENSEis already set.Test plan