You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
In some "languages" only allows complete comment lines but they do not allow to add comments to the same line as a statement. e.g. key=value in java .properties files.
Or in multi line shell script statements. Between the lines it is not possible (without tricks) to place a comment with gitleaks:allow Example:
echo 1 &&
echo 2 &&
echo "detected secret" &&
echo 4
Describe the solution you'd like
Enhance gitleaks:allow so that it is also usable before or after the line with the secret.
e.g:
gitleaks:allow_next_line
or better:
gitleaks:allow_line:+1 (the leak to allow is 1 lines beyond it; so in the next line)
gitleaks:allow_line:+3 (the leak to allow is 3 lines beyond it)
gitleaks:allow_line:-3 (the leak to allow is 3 lines before it)
Describe alternatives you've considered
Putting fingerprint to .gitleakignore
Is your feature request related to a problem? Please describe.
In some "languages" only allows complete comment lines but they do not allow to add comments to the same line as a statement. e.g. key=value in java .properties files.
Or in multi line shell script statements. Between the lines it is not possible (without tricks) to place a comment with gitleaks:allow Example:
echo 1 &&
echo 2 &&
echo "detected secret" &&
echo 4
Describe the solution you'd like
Enhance gitleaks:allow so that it is also usable before or after the line with the secret.
e.g:
gitleaks:allow_next_line
or better:
gitleaks:allow_line:+1 (the leak to allow is 1 lines beyond it; so in the next line)
gitleaks:allow_line:+3 (the leak to allow is 3 lines beyond it)
gitleaks:allow_line:-3 (the leak to allow is 3 lines before it)
Describe alternatives you've considered
Putting fingerprint to .gitleakignore
cc @zricethezav
The text was updated successfully, but these errors were encountered: