-
Notifications
You must be signed in to change notification settings - Fork 95
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
Comments
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. |
This would be fairly easy to implement in |
I take advantage of it not being recursive by default - if anything it should be a flag |
I would assume it would be a flag.
…On Mon, Mar 23, 2020 at 9:57 AM Patrick Lee Scott ***@***.***> wrote:
I take advantage of it not being recursive by default - if anything it
should be a flag
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#203 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEHOX6VNUM5XI6IHI3TQ4LRI52EBANCNFSM4JUJVELA>
.
|
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. |
🚀 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.The text was updated successfully, but these errors were encountered: