Consider cleaning up the commit history by removing binary files from it. #9
Description
Activity
Just saw these suggestions you submitted. Not a bad idea, thanks for pointing it out 🙂. @coolcoder613eb, I suppose you're fine with this too?
@Zardshard I'm bit late, but yes.
Reacted by Zardshard@Zardshard Should we close this issue? Is it too late now?
I think people can just clone with --depth if they don't want the binaries.
There are 3 people with forks that GitHub knows about, so it shouldn't be too late yet. It's just once we rewrite the history, all of the contributors will need to update to the new history. If a repository has too many contributors, it could become a headache to support so many people in switching. But I think it's still relatively simple to get everyone to update currently.
Reacted by OscarL and coolcoder613ebOh, just the contributors need to update? That's not too bad.
Cloning this repo is "a bit of a pain" on slow connections (not to mention wasteful in storage), due to older commits that included all the .so files. Good thing git clone --depth=1 exists, but...
Would it be possible to use git rebase -i to edit those olds commit, removing the binary files, and force-pushing the results back?
So far this project has only 2 forks (publicly, and here on GH at least), so that's only 2 people that will need to basically "re-clone" our forks. Better now than later, I think.