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

git clone depth #219

Closed
jayvdb opened this issue Feb 3, 2019 · 3 comments
Closed

git clone depth #219

jayvdb opened this issue Feb 3, 2019 · 3 comments

Comments

@jayvdb
Copy link
Member

jayvdb commented Feb 3, 2019

moban doesnt need a complete copy of the history. It only needs to be able to sync to the latest from each revision.

clone depth should be something like 2 to reduce unnecessary packs being fetched.

@chfw
Copy link
Member

chfw commented Feb 3, 2019

good idea!

@chfw
Copy link
Member

chfw commented Feb 4, 2019

when moban tries to update the repos, is this update command right?

git fetch origin --depth=1 for getting latest head

I assume, if git pull would get everything by default.

@jayvdb
Copy link
Member Author

jayvdb commented Feb 8, 2019

Yes

@chfw chfw mentioned this issue Feb 16, 2019
@chfw chfw closed this as completed Feb 17, 2019
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