-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Repo size is unnecessarily big due to old images commited directly to repo #1503
Labels
Comments
There's some other weird stuff in the history too. Looks like somebody committed Files
|
All binary files in history
|
Open
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the earliest days of this project, some images were directly committed to the repo 馃槥
This has made the repo unnecessarily large. It's currently (874081c) at 98M.
You can list all objects in the repo and sort by size with:
I've included a list of unused images and their sizes below:
We've got a 30MB jpg tumor! 馃が
For curiosity's sake, I've used the bfg repo cleaner to remove these files from the history of the repo. You can see the result here. The size of the clean repo is just 10MB! In other words, 90% of the data stored in our repo are these dead-weight images.
I'm not necessarily advocating that we actually implement the clean repo, because rewriting history can be more trouble than it's worth. If we were to do this, there are a couple common strategies.
Anyway, this is here for informative purposes and discussion.
The text was updated successfully, but these errors were encountered: