Closed szero2one closed 4 years ago
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 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.
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 notifications@github.com 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 https://github.com/mateodelnorte/meta/issues/203#issuecomment-602651695, 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.