Git repository might need some cleanup

[dvehrs]

I've got this cloned onto my system and the directory takes up 778M of which 380M is the .git directory. This seems excessive. Might it be worthwhile to run garbage collection and pruning to reduce this down a bit? Or is there a valid reason to keep it all that I'm missing?

Maybe run something like what is suggested here:
https://stackoverflow.com/questions/2116778/reduce-git-repository-size

[danielmiessler]

Phenomenal point. We'll look into it.

I'll keep it open until we get it resolved.

[shel3over]

you can use
git clone --depth 1
to clone the current state only ,without all the history

[dvehrs]

That's a good trick, shel3over.

From a quick test. An updated clone with full history was 764M but a fresh clone with --depth 1 was only 508M. The difference appears to be in the .git folders (448M vs 191M).

Maybe a note on the opening page to let users know this is a recommended way to clone?

[toxydose]

you can use
git clone --depth 1
to clone the current state only ,without all the history

I suggest to add this note with the notification about over-sized .git directory to README file before this issue will be fixed.

[kingthorin]

Note: If you use git clone --depth 1 it'll be less to transfer and have on disk, however, you also won't be able to push or open PRs (in my experience).

[vonProteus]

maybe migrate to git lfs
that would speed up the cloning process

[molangning]

maybe migrate to git lfs that would speed up the cloning process

lfs has GiB bandwidth per month, and any additional bandwidth needs to be purchased.

[ItsIgnacioPortal]

lfs has GiB bandwidth per month, and any additional bandwidth needs to be purchased.

To quote the github docs:

When you download a file tracked with Git LFS, the total file size is counted against the repository owner's bandwidth limit.

If you use more than 1 GiB of bandwidth per month without purchasing a data pack, Git LFS support is disabled on your account until the next month.

Also, if seclists were to use git LFS, everyone who wanted to clone the repo would also need to install git LFS on their system before cloning. See: https://docs.github.com/en/repositories/working-with-files/managing-large-files/collaboration-with-git-large-file-storage

Therefor, git LFS is not viable to be used on Seclists.