Bugzilla – Full Text Bug Listing
| Summary: | Cloning a repo to existing project cleans this project contents | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Malgorzata Janczarska <malgorzata.tomczyk> |
| Component: | Git | Assignee: | Project Inbox <orion.git-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | johnjbarton, ken_walker, tomasz.zarna |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
I think the current clone-into-folder is just broken. If I am on unix command line in current directory foo/ and issue git clone <url> then a new subdir is created in foo/ When I issued clone on the orion page and selected folder 'testcases' I expected the clone to land in a subdir of testcases/. I did not expect testcases to be overwritten. Rather than supporting over-write, it would be simpler for the use and orion to require that users delete existing directories if they want to overwrite them. (In reply to comment #1) So the problem is that you expected the repository to be cloned into a subfolder with a name same as a name of the repository? Cloning repository without specifying any directory is an equivalent of "git clone <url>" command that clones repository to a subfolder of your current directory, which, in Orion, is your workspace. Cloning repository to existing directory is equvalent to "git clone <url> <path>" that clones a repository to a given <path> without creating a subdirectory. With current workflow you can clone a repository to a folder of a different name and if you want a subdirectory you can always create it. I've been using it for a while and I find it more convenient, but I also understand your point. I think what misses is a possibility to create a subfolder of a given name while cloning. I can see something like "create subfolder" checkbox on directory choosing dialog and a default name of the folder as a name of the repository. Closing as part of a mass clean up of inactive bugs. Please reopen if this problem still occurs or is relevant to you. For more details see: https://dev.eclipse.org/mhonarc/lists/orion-dev/msg03444.html |
1. Clone a repository to an existing directory 2. Verify that repository contents is placed in the directory 3. Clone another repository to the same directory as in point 1. 4. Cloning ends with an error (error 500 while running operation: Destination path "ar" already exists and is not an empty directory) [GOOD] 5. The target directory is now empty, all its contents has been removed [BAD] I think the contents of the directory shound't be removed when cloning fails. I think we should also think of a way to display a warning ("Add contents of directory [...] will be removed, do you want to continue?").