You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When cloning very large repositories only for testing their functionality, not all previous commits are needed. Therefore the amount of commits to be cloned can be limited with the --depth flag in git.
Implementing it (-d/--depth) and passing it on to git could greatly help to keep the file size of the projects low.
The text was updated successfully, but these errors were encountered:
Thank you for this information, it hadn't occured to me to consider a shallow clone. Also the readme warns about this, if one wanted to work with it (emphasis mine):
With '--shallow' option, a "shallow clone" will be performed (for Git repositories only, 'git clone --depth 1 …' eg.). Be careful that a shallow-cloned repository cannot be pushed to remote. Currently Git and Mercurial repositories are supported.
@lorentzleutgeb May I ask what had once led to your 👎🏽 reaction on this post? I wasn't intending any harm here. 🤷🏽
When cloning very large repositories only for testing their functionality, not all previous commits are needed. Therefore the amount of commits to be cloned can be limited with the
--depth
flag in git.Implementing it (
-d
/--depth
) and passing it on to git could greatly help to keep the file size of the projects low.The text was updated successfully, but these errors were encountered: