将它放到一个每天晚上(下午?)当您睡觉时运行的cron作业中。

最新版本的git在需要时自动运行gc，所以你不需要做任何事情。参见man git-gc(1)的Options部分:“一些git命令在执行可能创建许多松散对象的操作后运行git gc——auto。”

你可以在没有任何中断的情况下，使用新的(Git 2.0 Q2 2014)设置gc.autodetach。

参见commit 4c4ac4d和commit 9f673f9 (nguyshape Thái ngeconc Duy, aka pclouds):

Gc—auto需要时间，并且可以暂时阻止用户(但也不那么烦人)。 让它在支持它的系统后台运行。 在后台运行唯一丢失的是打印输出。但是gc输出并不是很有趣。 你可以通过修改gc.autodetach来保持它在前台。

从2.0版本开始，就有一个bug: git 2.7(2015年Q4)将确保不会丢失错误消息。 参见commit 329e6e8 (19 Sep 2015) by nguyThái ngeconc Duy (pclouds)。 (由Junio C Hamano合并- gitster -在commit 076c827, 2015年10月15日)

gc: save log from daemonized gc --auto and print it next time While commit 9f673f9 (gc: config option for running --auto in background - 2014-02-08) helps reduce some complaints about 'gc --auto' hogging the terminal, it creates another set of problems. The latest in this set is, as the result of daemonizing, stderr is closed and all warnings are lost. This warning at the end of cmd_gc() is particularly important because it tells the user how to avoid "gc --auto" running repeatedly. Because stderr is closed, the user does not know, naturally they complain about 'gc --auto' wasting CPU. Daemonized gc now saves stderr to $GIT_DIR/gc.log. Following gc --auto will not run and gc.log printed out until the user removes gc.log.

你不需要经常使用git gc，因为git gc(垃圾收集)在几个常用的命令上自动运行:

git pull
git merge
git rebase
git commit

来源:git gc最佳实践和常见问题解答

这句话摘自; Git版本控制

Git runs garbage collection automatically: • If there are too many loose objects in the repository • When a push to a remote repository happens • After some commands that might introduce many loose objects • When some commands such as git reflog expire explicitly request it And finally, garbage collection occurs when you explicitly request it using the git gc command. But when should that be? There’s no solid answer to this question, but there is some good advice and best practice. You should consider running git gc manually in a few situations: • If you have just completed a git filter-branch . Recall that filter-branch rewrites many commits, introduces new ones, and leaves the old ones on a ref that should be removed when you are satisfied with the results. All those dead objects (that are no longer referenced since you just removed the one ref pointing to them) should be removed via garbage collection. • After some commands that might introduce many loose objects. This might be a large rebase effort, for example. And on the flip side, when should you be wary of garbage collection? • If there are orphaned refs that you might want to recover • In the context of git rerere and you do not need to save the resolutions forever • In the context of only tags and branches being sufficient to cause Git to retain a commit permanently • In the context of FETCH_HEAD retrievals (URL-direct retrievals via git fetch ) because they are immediately subject to garbage collection

我使用git gc后，我做了一个大的签出，并有很多新对象。它可以节省空间。例如，如果您使用git- SVN签出一个大型SVN项目，并执行git gc，通常可以节省大量空间