search

N0MoreSecr3ts / wraith

Uncover forgotten secrets and bring them back to life, haunting security and operations teams.
MIT License
206 stars 42 forks source link

How to use 'commit-depth' in config.yml? #117

Closed BrunoJu closed 2 years ago

BrunoJu commented 3 years ago

What's the meaning of this configuration item in config.yml

commit-depth = 1

mattyjones commented 2 years ago

@BrunoJu commit-depth refers to how deep into the commit history you want to scan. Ex. A depth of 100 means you want to scan the last 100 commits.

I am not sure why it was set to 1, my only thought was we were looking at doing a shallow clone of just the current working copy. The default is -1 which implies that it is a full commit depth to the bottle of the rabbit hole. All other numbers imply a true commit depth so they would not make sensible defaults. Using 9999999999 as a default is also a mess so I went with -1 as that is never going to be a commit-depth.