-
Notifications
You must be signed in to change notification settings - Fork 8
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
Committed database files bloating repo size #62
Comments
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>
.
|
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, |
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.
|
@DannyWeitekamp @cmaclell Are we good here? |
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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 @cmaclell
Github says the repo is 26.4MB. 25.5MB of that is db.sqlite3 files.
The text was updated successfully, but these errors were encountered: