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
As you can see, the file 2.c has been reported, but it is no longer in the tree. If there was git commit's SHA1 in the output - it would be easier to track when and who leaked the secret
Thanks
The text was updated successfully, but these errors were encountered:
Currently there is no way to know which revision has caused the leak.
For example:
As you can see, the file 2.c has been reported, but it is no longer in the tree. If there was git commit's SHA1 in the output - it would be easier to track when and who leaked the secret
Thanks
The text was updated successfully, but these errors were encountered: