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
My expectation is that pre-commit on a given commit and scan-local-repo just after the commit is added returns the same results.
If pre-commit says "all clear", and the commit is added, if I run scan-local-repo just after, it shouldn't flag as a problem the exact same commit that pre-commit was happy with.
However that does not seem the case, pre-commit lets a commit go through that is right after flagged by scan-local-repo.
🐛 Bug Report
My expectation is that pre-commit on a given commit and scan-local-repo just after the commit is added returns the same results.
If
pre-commit
says "all clear", and the commit is added, if I runscan-local-repo
just after, it shouldn't flag as a problem the exact same commit thatpre-commit
was happy with.However that does not seem the case,
pre-commit
lets a commit go through that is right after flagged byscan-local-repo
.To Reproduce
Switching tartufo back to some 2.x versions make it work correctly, so something changed between versions 2 and 3.
Expected Behavior
Tartufo v3 should behave here like tartufo v2 and detect the problem at
pre-commit
step.Code Example
N/A
Environment
See above. Python 3.9, tartufo 3.1.3 and 2.10.1 as comparison.
The text was updated successfully, but these errors were encountered: