-
Notifications
You must be signed in to change notification settings - Fork 3
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
reduce repo size #88
Comments
@ebgoldstein Yes, I was thinking eventually, for neatness sake, the archives would be available to the program to download from a separate source. It is a bit unorthodox to have the generated catalogs distributed with the code, but having the catalogs available (which they are on the fig-share site) is crucial for people who don't want to have to download all the archives to see data that has already been discovered before! |
@Matmorcat — ok, so i can move the archives to a seperate place (likely another github repository). It's a good point that it's helpful for people who may want to know what is available w/o downloading all the files (saying this as i have a work computer that has spent 2 fulls days of downloading just the florence archives 😆 ).. also btw — The catalogs are not in the figshare repository (only the tags).. I can remove them tommorrow and then close this issue. |
Also, you should look at BFG Repo-Cleaner to help remove the large files from the git history. If you don't, even if you delete them, they will still be in the history and the repo will still be large. |
i removed the catalogs. I am a bit scared of dealing with the git history.. if someone else wants to be brave, feel free... otherwise i will leave it for now out of fear. |
I had a go at cleaning the history, but couldn't push it back to the repo due to permissions. Someone else can run these commands and clean the history. You'll need a bit of a workaround since you can't specify the full path with BFG though. More details on the bfg page. Good luck if you decide to try this! In the repo, use git rev-list and grep to get the id's of the blobs for files in the
Save these blobs to
Run BFG to remove the blobs specified in
Prune the history:
Push back the repo:
|
generally we might just reduce the repo size (i.e., remove catalogs, since the module can build catalogs)...
Chris even mentioned it in his review, which i have turned into an issue: #86
I know our the JOSS bot had troubles building the paper because the repo was big (see the review issue).. originally I wanted the catalog to be in the repo for search features, but that enhancement is a bit downstream.
@Matmorcat , are you ok if the catalogs are removed?
The text was updated successfully, but these errors were encountered: