SecLists icon indicating copy to clipboard operation
SecLists copied to clipboard

Git repository might need some cleanup

Open dvehrs opened this issue 8 years ago • 8 comments

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

dvehrs avatar Apr 30 '16 15:04 dvehrs

Phenomenal point. We'll look into it.

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

danielmiessler avatar Jul 08 '16 14:07 danielmiessler

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

shel3over avatar Oct 10 '16 17:10 shel3over

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?

dvehrs avatar Oct 10 '16 18:10 dvehrs

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.

toxydose avatar Oct 31 '18 21:10 toxydose

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).

kingthorin avatar Apr 24 '20 12:04 kingthorin

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

vonProteus avatar Oct 16 '20 17:10 vonProteus

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.

molangning avatar Nov 27 '23 16:11 molangning