We are currently on a very old version of Gitlab (6.0.1) and I am setting up a newer version (8.2.2) on a whole new machine (so it’s not an in place upgrade, rather a “manual” migration). This machine will eventually be given the same name as the original, so my plan is to set up an identical structure on the new version (i.e. all the groups and repos named the same) so that no one has to change their remotes’ URL.
Most of our current repos are in a Gitlab group called
All. In the filesystem this group is stored as
all, because that version of Gitlab converted all names to lowercase. This means most remote URLs are of the form
git@our-host:all/our_repo.git. I tried creating the same lowercase
all group in the new version but I get a “Path is reserved” error.
Is this group name really reserved for internal use or is it just the program just trying to stop me using a generic name? For some reason the name
All is allowed, but that would still break all the remote URLs. To change the URLs on everyone’s local clones as well as all the scripts we have that pull and push would be a bit arduous. Is there a way to force Gitlab to create the group anyway, if this doesn’t break any internals?