-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Suggestion: Github Cleanup (Branches, tags, some history leftovers) #6835
Comments
some files should be removed from git history, like addons/ofxAssimpModelLoader/libs/assimp/lib/ios/assimp.a it takes a while but this can make way for a lean git
|
now running the top 100 files, we can see none of them are useful now.
|
From actual OF git (without installing libs) we don't have any useful file with more than 10Mb. the biggest file is Batang.ttf
there is this nice tool, git-filter-repo which can remove blobs from history, like
after the command and reflog the repo goes down from 2.2Gb to 1.13Gb |
sounds like a great idea. |
Rewriting history should happen, it will just kill all concurrent PR’s as
every hash is changed all the way back to the first rewrite.
I would recommend we merge all the major PR’s first. We do need to remove
the binaries
…On Wed, 3 May 2023 at 3:57 am, Roy Macdonald ***@***.***> wrote:
sounds like a great idea.
Have you tried out BFG <https://rtyley.github.io/bfg-repo-cleaner/> ?
Might work for the task and claims to be a lot faster than the regular git
commands.
—
Reply to this email directly, view it on GitHub
<#6835 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGK2HFBJ3WWHS34AJOS6XTXEFDJ3ANCNFSM5MI3DRHQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
yeah - I am not in a rush to do a rewrite. |
See our 2017 discussion about this here: #5562 Also all the commands and even a chime in from the BFG creator :D! |
Sorry this discussion: #1805 (comment) |
The analysis then was:
Down to ~111MB - This would retain GIT stability for the future. |
I've done this process since this initial analysis in 2017 for numerous clients and game projects where the binaries were attached. Or in cases where a GIT LFS upgrade was performed. It caused chaos if any FORK or un pushed code was then compared or attempted to be merged as every history was then compared. I do think there will a moment we should do this. It's just a messy one. I can experiment again on another repo with an up to date analysis and code to do so |
I did a git clone just now (Aug.5, 2023), and was surprised by how long the download was taking. It turned out that it included almost 2Gb of .git/objects/pack files. Googling told me that "The packfile is a single file containing the contents of all the objects that were removed from your filesystem." So, it seems like it would be completely harmless, and also very easy, to remove those files. That single step would reduce the download size by almost 90%. |
I think this branches can be safely deleted
some tags can be cleaned to and kept for releases or intermediate builds
and recently I've cloned the openFrameworks repo to list the top 20 largest files in there, and it seems almost none should be part of the distribution anyway. here is the command
and the result
The text was updated successfully, but these errors were encountered: