search

github / git-sizer

Compute various size metrics for a Git repository, flagging those that might cause problems
MIT License
3.48k stars 139 forks source link

Detect & report tmp_pack files #80

Closed katrinleinweber closed 3 years ago

katrinleinweber commented 3 years ago

When git repack fails, it's possible that .git/objects/pack/tmp_pack_* files are left over. Since these are likely to be large, I suggest that git-sizer users could benefit from being informed about them, for example in the Biggest objects section.

mhagger commented 3 years ago

Thanks for the idea. Until now, git-sizer has only concerned itself with the logical structure of the repository, independent of how things are packed or the presence of unreachable objects, let alone things like temp files that may have been left behind by interrupted processes. Even though there have been requests to broaden git-sizer's scope, I think that it is better to keep its mission focused, and let other tools concern themselves with other types of repository on-disk problems, like cruft files. (This might arguably even be a nice feature to add to git fsck.)

So I will close this issue. If we decide to expand git-sizer's scope, we can always re-open it.