Repository navigation
Stop a pull request from configuring its own secret scan - #51
Merged
Merged
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
 |
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.
In one line: the Safety check no longer lets a PR silence the secret scanner with its own
.gitleaks.toml,.gitleaksignoreorgitleaks:allow, and it scansbase..headincluding merge commits (AUG-958).What you need to decide: nothing. Safety marks this PR needs-owner because it edits
safety.sh; the owner gave a standing OK for this CI standard.Risk: low, and it closes a real gap. Same file as the reviewed template (homebase
efd2ab8); only this repo's profile rule differs.