Large files being tracked in git

[bhillmann]

Approximately 700 mb are being tracked on old database files within the git repo. When trying to purge the files on a fork and switch over the database folder to git lfs, I run into this issue:

Git LFS: (0 of 8 files) 0 B / 237.83 MB Git LFS objects can not be uploaded to this public fork. Docs: https://github.com/contact Git LFS objects can not be uploaded to this public fork. Docs: https://github.com/contact

Since LFS is a part of github and not git, it might be in our best interest to use something else to download the database files.

[GabeAl]

Good point. I've moved all databases except the default to my site last release for this reason... Maybe it will help at least going forward. On May 13, 2016 12:45 PM, "Benjamin Hillmann" [email protected] wrote:

Approximately 700 mb are being tracked on old database files within the git repo. When trying to purge the files on a fork and switch over the database folder to git lfs, I run into this issue:

Git LFS: (0 of 8 files) 0 B / 237.83 MB Git LFS objects can not be uploaded to this public fork. Docs: https://github.com/contact Git LFS objects can not be uploaded to this public fork. Docs: https://github.com/contact

Since LFS is a part of github and not git, it might be in our best interest to use something else to download the database files.

— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub https://github.com/GabeAl/NINJA-OPS/issues/12