Clone into "path" not "name"

[gregbacchus]

This seems like a really useful tool, however I don't understand why it would clone into directories that use the project/group name rather than the "path" from Gitlab?

Maybe an option could be made to clone into directories based on the Gitlab path?

[kebroman]

+1 for using the rest path vs. project/group names

[ziegenberg]

This seems to be a duplicate of #25.

[ezbz]

@gregbacchus one issue with allowing this is that it will not be interchangeable across runs when use of the parameter changes

say u did one run with path and then another with names you will get a double structure, this complicates things

[ziegenberg]

This is correct. You would have to stick with one method. Or find some way to detect the way it was run the last time.

[ahmadalli]

@gregbacchus one issue with allowing this is that it will not be interchangeable across runs when use of the parameter changes

say u did one run with path and then another with names you will get a double structure, this complicates things

I'm new to this project and I'm not aware of the scope of its abilities, my question is what happens if users change the name of their project on gitlab? wouldn't that cause a double structure?

[ahmadalli]

also what will happen if there exists some projects with the same name on a group (since gitlab assures path uniqueness, not name uniqueness)

[gregbacchus]

@ezbz say u did one run with path and then another with names you will get a double structure, this complicates things

I don't see any problem there. Running with the same arguments is about as important as running it in the same target location. Changing either could result in duplication.

[ezbz]

what happens if users change the name of their project on gitlab? wouldn't that cause a double structure?

true that one project will be duplicate locally gitlabber doesn't maintain any local state (i.e., project ids)

[ezbz]

Duplicate of #25