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
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
TruffleHog Version
3.25.2
Expected Behavior
When running the Trufflehog the output containing the line number should match the line in the actual commit.
Actual Behavior
The lines do sometimes not match.
Steps to Reproduce
We are running Trufflehog on internal repositories with the command:
trufflehog git --only-verified
and the output in the terminal shows a line number. When searching for the commit in Azure DevOps the secret sometimes appears on a different line than stated in the output.
Environment
OS: macOS Monterey
Version 12.6
Additional Context
When the lines do not match, the line number in the commit is around five lines below or above.
The text was updated successfully, but these errors were encountered:
Community Note
TruffleHog Version
3.25.2
Expected Behavior
When running the Trufflehog the output containing the line number should match the line in the actual commit.
Actual Behavior
The lines do sometimes not match.
Steps to Reproduce
We are running Trufflehog on internal repositories with the command:
trufflehog git --only-verified
and the output in the terminal shows a line number. When searching for the commit in Azure DevOps the secret sometimes appears on a different line than stated in the output.
Environment
Additional Context
When the lines do not match, the line number in the commit is around five lines below or above.
The text was updated successfully, but these errors were encountered: