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

Support shallow clones #282

Open
bananer opened this issue Mar 14, 2022 · 3 comments
Open

Support shallow clones #282

bananer opened this issue Mar 14, 2022 · 3 comments

Comments

@bananer
Copy link
Contributor

bananer commented Mar 14, 2022

Passing --depth 1 to repo init causes all modules to be shallow clones. A quick test showed that this reduces the required disk space and time to download significantly - less than 100GB for the whole 18.1 tree before build.

I want to support this, but only as an opt-in, since it might break some peoples' workflow which assumes the whole history to be present.

@Robin-Sch
Copy link

Is it possible to "update" shallow clones by only downloading the new changes, without re-downloading everything?

@petefoth
Copy link
Contributor

Fixed by #431

@petefoth petefoth reopened this Sep 1, 2023
@petefoth
Copy link
Contributor

petefoth commented Sep 1, 2023

#431 did not fix this, and managed to break the build instead - see #478

Re-opened - the fix from #431 needs to be corrected (change ... repo init "$REPO_INIT_ARGS" ... to ... repo init "${REPO_INIT_ARGS}" ...

This issue can stay open till we get a PR that works ;)

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 a pull request may close this issue.

3 participants