We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some error might occur during clone of git repositories and seems to to be maanged properly.
See bellow some anonymized logs (cleaned data are in [%%]):
Cloning (73 / 189) **[%GIT CLONE SSH URL%.]**.. Cloning into 'server-hardening-collection'... remote: Enumerating objects: 696, done. remote: Counting objects: 100% (155/155), done. remote: Compressing objects: 100% (48/48), done. remote: Total 696 (delta 124), reused 119 (delta 105), pack-reused 541 Receiving objects: 100% (696/696), 195.25 KiB | 1.22 MiB/s, done. Resolving deltas: 100% (302/302), done. Downloading **[%TAR GZ GPG FILE OF 100 MB%.]** Error downloading object: **[%TAR GZ GPG FILE OF 100 MB%.]** (**[% COMMIT HASH %]**): Smudge error: Error downloading **[%TAR GZ GPG FILE OF 100 MB%.] **(**[% COMMIT HASH FULL%]**): batch response: Post **[%BATCH FILE URL%]**: proxyconnect tcp: dial tcp: lookup **[%PROXY%]:** no such host Errors logged to **[%LOG FILE %]** Use `git lfs logs last` to view the log. error: external filter 'git-lfs filter-process' failed fatal: **[% THE BIG GPG FILE%]** smudge filter lfs failed warning: Clone succeeded, but checkout failed. You can inspect what was checked out with 'git status' and retry with 'git restore --source=HEAD :/' Cloned in folder '**[% PROJECT NAME %]**' ○ │╲ │ ○ ○ ░ ░ gitleaks 7:31PM INF no leaks found 7:31PM INF scan completed in 266.537697ms **[%PATH%]** ✅ Gitleaks did not find leaks for 'server-hardening-collection'
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Some error might occur during clone of git repositories and seems to to be maanged properly.
See bellow some anonymized logs (cleaned data are in [%%]):
The text was updated successfully, but these errors were encountered: