Closed AmandaCameron closed 7 years ago
oh my… I did not know about that feature 😮
currently the code base is definitely not supporting subgroups, as the logic recognizing repo slugs is common to all services. So with a quick look (and remembering), I think that the culprits are:
I was already thinking of calling username
part of the slug more properly namespace
(that would cover the idea of subgroups) and remove the one slash constraint (which is not a technical constraint), when working on 2.0. But I guess gitlab has decided otherwise.
Sadly, I'm currently having 2 jobs at the same time, which does not leave me much time to actually work on this any time soon, but I'd be very happy to help anybody willing to jump on this! I'm always connected on IRC/Matrix/Gitter cf the Readme.
You're welcome to discuss all that on IRC, irc.freenode.org
/ #git-repo
. My status is that currently I'm totally snowed, having worked the last 3 months day in, day out, week ends included… And that project has lesser priority. I'd be happy to give commit access to trusted people, but it looks like I've not been good enough at creating a community around the tool! ☹
I've got a private gitlab instance which makes pretty heavy use of the subgroup feature added in GitLab 9.0, as a result I can't use this tool to clone, make a MR, etc for a repo that's in a subgroup (or, even a subgroup of a subgroup).