-
Hi, After step 4, the tags are not yet uploaded, so I ran For the first repo, this does not change the repo size a lot (42MB -> 43MB), and when exploring the source at this tag, the large files are gone, as expected. But for the second repo, pushing the tags increases repo size from 2MB to 100MB, and when exploring the source from the tag, all the large files are there again. I tried for hours, but fail to see what is different between the two repositories. Can someone clarify what the expected result is? Ideally I want to keep all tags, but have them rewritten so that they point to the new hashes. I also asked for help on stackoverflow: |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
It turns out there were several tags pointing to unreachable objects. |
Beta Was this translation helpful? Give feedback.
It turns out there were several tags pointing to unreachable objects.
The trick to work around it was to modify steps 1: Instead of cloning, do a git init, then remote add, then fetch --all and fetch --tags.
Fetch will only fetch reachable objects.
https://stackoverflow.com/questions/20647495/why-is-a-cloned-repo-10x-larger-than-a-fetched-repo