New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use shallow cloning #105

Merged
merged 2 commits into from Nov 29, 2017

Conversation

Projects
None yet
2 participants
@tristanpemble
Contributor

tristanpemble commented Nov 29, 2017

We have some big repositories. Forge really only needs the most recent revision when it pulls for itself. This speeds up initial setup for each of our repositories from ~3 minutes to 15 seconds.

Subsequent pulls need to be wary of the fact that they are working from a shallow repository. This could be weird since forge pull will pull all repos, including things outside of .forge. I don't know what will happen then.

@rhs rhs merged commit d63b822 into datawire:master Nov 29, 2017

1 of 2 checks passed

continuous-integration/travis-ci/pr The Travis CI build could not complete due to an error
Details
deploy/netlify Deploy preview ready!
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment