Workspace cloning including local clone path

10 votes

Some of our solutions contain projects from multiple repositories. Some of these projects are included in multiple solutions. So when cloned they have to be the correct relative path from each other.

Workspaces seem like the right idea for this.

However, I have two issues. The first is that they all get cloned into the same local directory using the project names as the folder name. It would be nice to be able to dictate, in the workspace, the name of the folder to clone each repository to make sure everything is in the correct relative directory for that solution.

Also, if the repositories are included in separate workspaces that they don't point to the same local repository. Due to needing them in a proper folder structure, we might need to clone to a different directory locally for each solution.

Thanks for your consideration!

Under consideration Suggested by: Charlie Upvoted: 05 Apr, '24 Comments: 0

Comments: 0