I seem to be having problems getting a repository down to size. I know one of the problems is a few rather large video files managed to make it up but it seems like no matter what I do I can't push up the changes, that would ignore, or remove these files. I'm considering just deleting the repo along with setting up new ones here, of course, all that history will be gone, but then I'm not sure If I've already broken that on this end. Not sure what to do from here, other then that.
Hi Micheal, welcome to the Community!
Have you followed the steps at Reduce repository size already? If so, what's the size of your local repo? Do you get any error when you try to force push it?
You also mentioned that the problem was caused by some large video files, DVCS systems such as Bitbucket are not good candidates for storing binary files, as Git or Mercurial will not work well with them. For binary or executable storage, we recommend you look into file hosting services such as DropBox, rsync, rsnapshot, rdiff-backup, and so forth, or enable Git LFS. For more info you can read Git Large File Storage.
Hope that helps!
Let us know if you have any more questions and we'll be glad to help.
Kind regards,
Ana
I was following the steps at that link, the problem is no matter what when I push the changes, it instantly comes back with over 2BG error. Having the videos go up was an unnoticed mistake. They were supposed to be listed in the .gitignore file. and not sent up. Something went wrong, obviously, and our noobness showed. That's one of the things we're trying to fix.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'll just add the project that we're working on is a VR app that shows 360 videos. I'm not trying to use this as normal file storage, they are actually part of the project. I am also trying to get LFS working to, mostly to try to head off things like this, but it looks like anything over like 10MB is a large file, so I may need it for PSDs with textures and stuff.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I ran through the whole procedure again. I've done something horribly wrong, as git count-objects size-pack has managed to almost double. At this point, it might just be easier to make a new project remove the offending files, and use where the code is at right now as a starting point.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.