Repository navigation
Conversation
Public GitHub repos cannot call private m0-pipelines reusable workflows. Host the secret-scan composite and org baseline here so protocol and other public repos can use the same EVM private-key rules.
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
1 participant
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
m0-pipelines. PYUSDx leftover Security already fails in 0s for that reason.gitleaks.tomlbaseline, andworkflow_callhere (this repo is already public) so callers can use:m0-pipelines(evm-32-byte-hex/bare-32-byte-hex). Repo.gitleaks.tomlstill extends the baseline viauseDefault = true.m0-pipelinessecret-scan at this repo so private and public share one copy.Test plan
@main)Test Gitleaks configfixtures are green