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

Repository clones into wrong folder #4193

Closed
zifik opened this issue Dec 15, 2020 · 2 comments
Closed

Repository clones into wrong folder #4193

zifik opened this issue Dec 15, 2020 · 2 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug containers Issue in vscode-remote containers

Comments

@zifik
Copy link

zifik commented Dec 15, 2020

Issue Type: Bug

My git repository is listed under a subgroup in a private GitLab instance. This makes my clone URL look like: [email protected]:myproject/subgroup1/subgroup2/myrepo.git

When using Remote-Containers: Clone repository in Container Volume..., and selecting Create a unique volume the folder that is created in the container is /workspace/subgroup1 when it should be /workspace/myrepo. All names for the project seen in the container also reflect subgroup1 and not myrepo.

This can potentially create issues with other projects in the same subgroup and creates confusion with identifying which container and which volume belongs to which project.

Please note that this also affects the volume name on the container host.

Extension version: 0.154.0
VS Code version: Code 1.52.0 (940b5f4bb5fa47866a54529ed759d95d09ee80be, 2020-12-10T22:45:11.850Z)
OS version: Windows_NT x64 10.0.18363
Remote OS version: Linux x64 5.4.0-58-generic

Update:
In an attempt to understand this more I realized that if I pick Create a new volume... with the intent of sharing among several repositories, then I get the opportunity to supply a name for the repo. It defaults to "subgroup1", but in overriding that with the actual name of the repo, the resulting docker image, container, volumes, and folder names all appear to be correct. I will proceed with this approach.

@github-actions github-actions bot added the containers Issue in vscode-remote containers label Dec 15, 2020
@egamma egamma added the bug Issue identified by VS Code Team member as probable bug label Feb 25, 2021
@J0F3
Copy link

J0F3 commented Mar 18, 2022

That's something that I noticed also (with GitLab) and my workaround was the same. So just using the Clone repository in Named Container Volume... and the specify the names by myself.

But I think it is still a bug that it picks ups the wrong names when using Clone repository in Container Volume where the names are automatically defined.

@chrmarti
Copy link
Contributor

Continuing in #5388. Thanks.

@github-actions github-actions bot locked and limited conversation to collaborators Jan 28, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug containers Issue in vscode-remote containers
Projects
None yet
Development

No branches or pull requests

4 participants