Committed database files bloating repo size #62

Activity

1. annarafferty commented on Jun 8, 2020

   

   annarafferty

   on Jun 8, 2020 via email

   Collaborator

   More actions

   Sorry - the fractrain stuff is from one of my students and shouldn't have been committed. I can delete from their branch, but I'm not sure precisely how to clean out of history. Sorry about that! Anna

   …

   On Sun, Jun 7, 2020 at 11:55 AM DannyWeitekamp ***@***.***> wrote: Here is a list of the largest files committed to this repo: size pack location 64050 18392 db.sqlite3 21031 5945 db.sqlite3 2857 919 db.sqlite3 1977 34 fractrain/getRules.csv 871 257 db.sqlite3 858 311 apprentice/learners/grammar.pickle 260 12 fractrain/MultOnly.txt 201 9 fractrain/condition2/ruleslog3 199 3 fractrain/ruleslog 196 66 ilp/FOIL6/foil6_mac I'm not sure what all of those are but I'm pretty sure those db.sqlite3 files ought not to have been committed. Do ya'll think we should clean those out of the history? @eharpste <https://github.com/eharpste> @cmaclell <https://github.com/cmaclell> Github says the repo is 26.4MB. 25.5MB of that is db.sqlite3 files. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#62>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAS76NHH3ICJ2D7WQQWY2L3RVPBBVANCNFSM4NXNPMFQ> .
2. DannyWeitekamp commented on Jun 8, 2020

   

   DannyWeitekamp

   on Jun 8, 2020

   CollaboratorAuthor

   More actions

   Hey Anna,

   Thanks for letting me know! When I start cleaning stuff out I'll keep that in mind. Don't worry about removing anything. I'm mostly shooting for the really big stuff.

   Best Regards,
   Danny
3. cmaclell commented on Jun 8, 2020

   

   cmaclell

   on Jun 8, 2020 via email

   Collaborator

   More actions

   Hey Danny, I think I was probably the initial culprit. I committed at least one version of the SQLite DB way back in the day. I did it for convenience (so I wouldn’t have to create the D.B. when cloning), but I think it is better to just remove it. Best wishes, Chris

   …

   Sent from my iPhone

   On Jun 8, 2020, at 3:40 PM, DannyWeitekamp ***@***.***> wrote:  Hey Anna, Thanks for letting me know! When I start cleaning stuff out I'll keep that in mind. Don't worry about removing anything. I'm mostly shooting for the really big stuff. Best Regards, Danny — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.
4. eharpste commented on Aug 6, 2020

   

   eharpste

   on Aug 6, 2020

   Member

   More actions

   @DannyWeitekamp @cmaclell Are we good here?
5. eharpste commented on Dec 7, 2020

   

   eharpste

   on Dec 7, 2020

   Member

   More actions

   Making a note that we have removed the db file from the current branch but we want to look into purging it from the commit history at some point.