Skip to content
This repository has been archived by the owner on Nov 1, 2022. It is now read-only.

Change git package to use a shallow git clone #487

Merged
merged 1 commit into from Mar 13, 2017
Merged

Conversation

squaremo
Copy link
Member

We only need the files from the git repo, and not the history. There are savings to using a shallow clone in this circumstance, in network traffic and disk space (and therefore in speed). The savings will depend on the repo, of course.

We only need the files from the git repo, and not the history. There
are savings to using a shallow clone in this circumstance, in network
traffic and disk space (and therefore in speed). The savings will
depend on the repo, of course.
Copy link
Contributor

@paulbellamy paulbellamy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

win!

@squaremo squaremo merged commit 954ea38 into master Mar 13, 2017
@squaremo squaremo deleted the git-shallow-clone branch March 13, 2017 15:34
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants