While you are here, I have a question. As far as I can tell neither your service nor Github nor Bitbucket have a way for a user to organize their repositories other than a list.
This gets annoying if one has many unrelated projects.
For instance, I have some chess projects, some math projects, some Warhammer Online projects, and so on. With the linear list approach if I want some semblance of order I need to resort to a kludge like prefixing the names with chess- and math- and WAR- and so on and using sort-by-name.
It would be a lot easier to deal with if I could have a chess folder and math folder and WAR folder and put the appropriate projects there. Even better would be multiple levels of folders, and allowing a project to be in more than one folder at a time.
In the project information, there is a field to enter a list of tags. I tried using that, with the idea that someone who wanted to see all my chess projects, say, could look for all projects I tagged "chess".
Two problems: (1) I could not figure out what these tags actually do other than show up on the project settings page, and (2) I could not find any help on them in the Gitlab documentation because searching for "tags" brings up a bazillion things about Git tags. Maybe these should be called "labels" instead of "tags"?
I see that there is a Groups feature, and I have not yet had a chance to delve into that to see if it can substitute for folders.
Unfortunately, it's only for teams right now, it seems. Additionally, (and this may only be a me concern) you can't include repos in more than one project, like in the case that you have a common framework you build between separate projects. I mentioned this to them (may have even had a support request), but haven't gotten any feedback.
Basically, it's much more rigid that I personally find useful, but it seems like their first step in the right direction.
[Edit] Seems kannonboy said the same thing, but I'll leave my opinions here. Interested to see if anyone else has used it and has any opinions.
There are two things that might be relevant to your request. In GitLab you can star repo's and show that, obviously this would mean only one list. And we would love to see nested groups https://gitlab.com/gitlab-org/gitlab-ce/issues/2772 although this would require you to move the projects under the chess namespace.
It seems like you guys are proceeding down the directories path to solve this issue-is there any reason that semantic tagging wasn't considered? It would appear to be a good fit and might solve the nesting issue, but I could have totally missed some conflicting requirements. (I admit I was flipping through the issue thread fairly quickly)
Definitely agree. I have a project that has iOS, server, and android reopos and it'd be nice to have there be some notion that they're related, maybe even have issues sharable? Though I guess that could get really messy.
