Shallow clones used to be somewhat impaired citizens of the Git world as some operations were barely supported. Tip: Build systems connected to your Git repo benefit from shallow clones, too! The benefit grows proportionately to how many binary assets your project has swallowed over time. A shallow clone of the repo takes 29.5 seconds, compared to 4 minutes 24 seconds for a full clone with all the history. The full clone of Jira is 677MB, with the working directory being another 320MB, made up of more than 47,000+ commits. The time savings for repos like this can add up and be very noticeable. For example, we migrated Jira (an 11 year-old code base) to Git. Imagine you accumulated ten or more years of project history in your repository. How do you do it? Just use the –depth option. Git’s shallow clone option allows you to pull down only the latest n commits of the repo’s history.
The first solution to a fast clone and saving developer’s and system’s time and disk space is to copy only recent revisions. Some repos have to be kept in tact for legal or regulatory reasons. And you can’t always avoid long histories. Cloning repositories with a very long historyĮven though threshold for a qualifying a repository as “massive” is pretty high, they’re still a pain to clone. The techniques and workarounds for each scenario are different, though sometimes complementary. But there’s a moderately easy – if annoying – fix for that (see below). Sometimes the second type of problem is compounded by the fact that old, deprecated binary artifacts are still stored in the repository. They include huge binary assets that need to be tracked and paired together with code.They accumulate a very very long history (the project grows over a very long period of time and the baggage accumulates).
If you think about it there are broadly two major reasons for repositories growing massive: In this post I’ll give you some techniques for dealing with it. But what happens when the repository you want to track is really really big? Git is a fantastic choice for tracking the evolution of your code base and collaborating efficiently with your peers.
0 kommentar(er)
