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

Recursive cloning (covering nested meta repos) #203

Closed
szero2one opened this issue Dec 2, 2019 · 5 comments
Closed

Recursive cloning (covering nested meta repos) #203

szero2one opened this issue Dec 2, 2019 · 5 comments

Comments

@szero2one
Copy link

🚀 Feature Proposal

meta git clone <project> currently clones a single layer in. If you have a meta-repo within a meta-repo, it will only clone the direct children of the root meta repo. Would be great if it automatically detected sub meta repos, and performed the clone all the way down the subtrees.

Motivation

Practical experience. Would be convenient.

Example

meta git clone <project> - clones everything.

@szero2one
Copy link
Author

On a second thought, the only thing needed here may be an addition to the docs. Especially if the feature would be cumbersome to implement.

You can totally get by without nested meta-repos, but likely more people will run into this issue, so I added a PR.

@mateodelnorte
Copy link
Owner

This would be fairly easy to implement in meta-git-clone. You would just have to detect the presence of a .meta file in a newly cloned repo. Happy to field a PR if someone wants to make it.

@patrickleet
Copy link
Collaborator

I take advantage of it not being recursive by default - if anything it should be a flag

@mateodelnorte
Copy link
Owner

mateodelnorte commented Mar 23, 2020 via email

@stale
Copy link

stale bot commented May 22, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label May 22, 2020
@stale stale bot closed this as completed May 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants