April 5, 2016

Better Narrow Cloning with GitSwarm

Git at Scale

A few months ago I blogged about Narrow Cloning with GitSwarm, a feature Git developers have needed for some time. Today I’m circling back to the same topic because our new release of GitSwarm, 2016.1, makes it even easier than before.

To summarize, narrow cloning used to require editing configuration files for our back-end connector technology, Git Fusion. Since then the GitSwarm elves have been hard at work on improving this process and have arrived at the following bit of new user interface on the project creation page:

This new option, to select directories to mirror, makes it easy to pick various existing locations and use them as branches in a new Git repository. The new UI doesn’t cover every possible configuration option—for that you’ll want to review the syntax in the earlier blog—but it should cover the majority of use cases based on the feedback we’ve received.

The way it works is simple: cherry pick whatever existing content you like, give them branch names, and create your project. The work of assembling a Git repo will be done for you behind the scenes, and you’ll be cloning only that Git-sized slice of a huge Helix monorepo in no time.

As before, GitSwarm 2016.1 is available for download and free for evaluation purposes and small teams. Give it a try and see if you can’t slice off only what you need. Your network and disk will thank you for it.