Skip to content

Conversation

@kamocat
Copy link

@kamocat kamocat commented May 18, 2022

The git clone can be sped up substantially by skipping the commit history, using the "--depth 1" option.
Anyone who actually wants the commit history can get it with "git pull" or by looking online.

The git clone can be sped up substantially by skipping the commit history, using the "--depth 1" option.
Anyone who actually *wants* the commit history can get it with "git pull" or by looking online.
@ESP-Marius
Copy link
Collaborator

Thanks for you suggestion!

I agree that in many cases doing a shallow clone is better, but for our getting-started guide I still think we should recommend doing a full clone.

We had an internal discussion about this a while ago, and the conclusion was that we should keep it as simple and straight-forward as possible, with the least amount of surprises for users. If we changed it to a shallow clone we would also have to add an explanation and mention the consequences of this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants