Replies: 2 comments 1 reply
-
Hi @lindell, can you take a look when you have time? Thanks! |
Beta Was this translation helpful? Give feedback.
0 replies
-
I see many people needing to use this. So a command might be useful. The only counter argument to adding this is that you could do it with the print command and a one line script already.
But it might not be that discoverable which is a counter argument to the counter argument. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I needed to clone a large number of repos from org, crawl those files for specific information, and generate a dashboard for an org's repos. I added a clone command to multi-gitter on my fork for the first part of that task:
master...cburch824:master
In short, the clone command preserves the org/group/repo structure when repos are cloned down:
.
├── company1 # Org / Top Level Group
│ ├── repo1 # repo1
│ ├── repo2 # repo2
│ └── group1 # Group 1
│ └── repo3 # repo3 under Group 1
└── ...
Would this feature be a potential candidate for a PR into the main repo?
Beta Was this translation helpful? Give feedback.
All reactions