Replies: 2 comments
-
|
secretlint does not lint for commit history by default #34 #211 Something is wrong. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I should have mentioned that this is during CI checks in a PR on GitHub. Manual run of secretlint in local cloned copy of repository does not produce the same error. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Summary
Relevant information
How do you ignore the error reporting of a private key that is found in the commit history of a GitHub repository? The key is deleted and not in use but the error is still there because of the commit history.
Error is flagged during CI checks on a GitHub pull request. Error is not reported during manual run of secretlint on local cloned repository.
Environment (if relevant)
secretlint v5.2.3
Beta Was this translation helpful? Give feedback.
All reactions