如何在运行BFG Repo Cleaner后更新/缩小我的github repo的大小

本文介绍了如何在运行BFG Repo Cleaner后更新/缩小我的github repo的大小的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！

问题描述

我使用以下的回购清单。 /rtyley.github.io/bfg-repo-cleaner/#usage\">程序：

 在您的回购站点上，并不意味着GitHub已在他们的回购副本将会显得更大一段时间，即使你克隆它时，只会发送'基本'信息，所以你会收到你想要的更小的回购。  
 
  完全披露：我是BFG Repo-Cleaner的作者。 I have cleaned my repo with BFG Repo Cleaner using the following procedure:
$ git clone --mirror git://example.com/some-big-repo.git
$ java -jar bfg.jar --strip-biggest-blobs 500 some-big-repo.git
$ cd some-big-repo.git
$ git reflog expire --expire=now --all
$ git gc --prune=now --aggressive
$ git push
I can see that my local repo has shrunk with 1GB. Great. The problem that I'm having now and that I haven't been able to find any info on is that now I would like to also shrink the size of the GitHub-repo as well. How to achieve this?
git push didn't work and I also tried git push origin --force --all which gave me this error message: error: --all and --mirror are incompatible
 解决方案 
My advice: don't worry too much about what GitHub reports as the repo size. For various reasons it won't accurately reflect the 'true' size of the repo.
What you really care about is the answer to this question: 
How big is this repo on my disk if I do a fresh clone of it from GitHub?
The amount of data you have to download to do a fresh clone of your repo, and the amount of space it takes up on your disk, are the things you really care about (and nearly identical quantities). Try doing a fresh clone and seeing how much data gets transferred and how much room it takes up on your disk. It should match the size of your shrunken repo.
The number reported in the GitHub console (ie at https://github.com/settings/repositories, or in the GitHub API) is not really important to you, which is fortunate, because it enjoys a liberated and somewhat drunken relationship with the more important figure above, due to the use of Git Alternates, and git gc occurring only periodically on GitHub servers. 
Side note: Bitbucket can also take time to update reported repo size.
Just because you ran git gc locally on your repo, doesn't mean GitHub have run it on their copy of your repo yet, and so their copy of your repo will appear much bigger for a while, even though when you clone it, only the 'essential' information is sent, and so you receive the smaller repo that you desire.
Full disclosure: I'm the author of the BFG Repo-Cleaner.
                        这篇关于如何在运行BFG Repo Cleaner后更新/缩小我的github repo的大小的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！