Hi, I am using Michael's fantastic Git repo analyzer tool "git-sizer" [*] and it detected a very large commit of 7.33 MiB in my repo (see chart below). This large commit is expected. I've imported that repo from another version control system but excluded all binary files (e.g. images) and some 3rd party components as their history is not important [**]. I've reintroduced these files in the head commit again. This is where the large commit came from. This repo is not used in production yet but I wonder if this kind of approach can cause trouble down the line? Are there any relevant implication of a single large commit like this in history? Thanks, Lars [*] https://github.com/github/git-sizer [**] I know some of this stuff shouldn't be in the repo in the first place, but I am constrained in the things I can change. ####################################################################### ## git-sizer output Processing blobs: 543782 Processing trees: 517104 Processing commits: 43365 Matching commits to trees: 43365 Processing annotated tags: 3 Processing references: 123 | Name | Value | Level of concern | | ---------------------------- | --------- | ------------------------------ | | Overall repository size | | | | * Blobs | | | | * Total size | 18.8 GiB | ** | | | | | | Biggest objects | | | | * Commits | | | | * Maximum size [1] | 7.33 MiB | !!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | | * Trees | | | | * Maximum entries [2] | 6.84 k | ** | | | | | | History structure | | | | * Maximum tag depth [3] | 1 | * | | | | | | Biggest checkouts | | | | * Number of directories [4] | 21.9 k | ********** | | * Maximum path depth [4] | 18 | * | | * Maximum path length [5] | 225 B | ** | | * Number of files [4] | 256 k | ***** | | * Total size of files [6] | 2.08 GiB | ** |
