Skip to content

Use partial clone strategy #177

@thatbudakguy

Description

@thatbudakguy

Cloning a large number of repositories with their full history is an expensive operation, both in terms of network and disk/inode usage. In most cases we don't need the full history of changes, especially since the user can find them on github, so we can use a partial strategy to save on resources.

In addition to the classic --depth=1 ("shallow clone") strategy there's now apparently something called a "blobless clone" that saves on resources but doesn't sacrifice as much as removing the history entirely. For more info, see this article on partial clone strategies.

Related to #155 which might support this more easily.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions