search

bogdanfinn / tls-client

net/http.Client like HTTP Client with options to select specific client TLS Fingerprints to use for requests.
BSD 4-Clause "Original" or "Old" License
670 stars 133 forks source link

The repository size is too large #42

Open nacho00112 opened 1 year ago

nacho00112 commented 1 year ago

You should consider reducing the repository size by some way, this isn't normal

nacho00112 commented 1 year ago

GitHub recommend to maintain every project behind 1GB, your repository is being too close to this, the repositories normally not even reach the 100MB

bogdanfinn commented 1 year ago

@nacho00112 yes the problem is that back then i had the compiled binaries inside the repository because most of the users were not able to compile them alone.

i removed that and placed the binaries in the release section of github but they are still in the history... i would have to revisit every commit and manually remove the files from the history which would result in a ton of new commits and a possible force push ...

See this SO answer for more information: https://stackoverflow.com/a/52643437

i'm not sure if i really should do it because this repo already has 53 forks ...

maybe someone has a better idea/solution?

sleeyax commented 2 months ago

git-extras has an easy to use git obliterate sub-command that makes removal of junk trivial. It automatically rewrites the entire repo history for you.

Unfortunately a force push is required and it will mess up all active forks, there's no way around that as far as I know.