Skip to content
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

shallow clone option #23

Open
hedgehog opened this issue Jun 29, 2011 · 2 comments
Open

shallow clone option #23

hedgehog opened this issue Jun 29, 2011 · 2 comments

Comments

@hedgehog
Copy link
Contributor

When deploying to production it is quite plausible that you won't need to do the things that shallow clones stop you from doing.
Also you can often take a 6MB download and reduce it to 100kB - speeding deployment.

 repository: "https://github.com/username/project.git"
 branch: "staging"
 depth: "1"
@rick
Copy link
Member

rick commented Jun 29, 2011

I might make this available on a per-repository basis. It'll require some noticeable documentation on the pitfalls. I always preferred shallow clones (though the stats you can find online point to there not being as big a win as one would at first think), but it's funny how easy it is for people to do things that make them break.

@hedgehog
Copy link
Contributor Author

Yep, +1 on the neon lights warning. It should only be used in a production setting where any change is one way.

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

No branches or pull requests

2 participants