This repository has been archived by the owner on Apr 18, 2024. It is now read-only.
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.
Override default gitleaks configuration
We use default gitleaks rules. These rules sometimes have some flaws, e.g. we have a lot of false positives for the Twitter Client IDs because of the default Twitter rules (more information). To fix this problem I override the default gitleaks rules with the rules provided by this repository (
/gitleaks.toml
).Also, I set a reasonable default (
.of/security/gitleaks.toml
) for theconfig-path
input argument and fix its description to reflect the fact that it's not the main configuration file but an additional config.Questions
v1.6.0-of-custom
or update all the repositories to use the new version of motain/gitleaks-action