Group Scoped Tags for Enterprise Software Development Projects
As a person building applications that are composed of many separate Git repositories, I find it useful to avoid mega-repositories, instead I use multiple git repositories that I control directly, and I create tags when I make a release. Maybe I have a rule that I always tag all git repos with the same tag names, or maybe they are related by rules known to me, that Gitlab can't infer automatically.
When I release version 8.14 of a product that consists of about 8 in-house git repos, and about as many upstream or external projects, it could be very nice to go to Gitlab's Group page, and have a new Tags sub page at the scope where I currently only see "All Projects | Shared Projects". At this "Tags" level I would like to see a list of related-tags that exist in various repos inside this Gitlab Group entity, and perhaps even have "external" foreign repository tag+URL references. I have made a mockup that should be obvious in utility to anybody who for example, might want to know "what git revision of Gitlab CE shipped in v8.14, and what git revision of Gitlab EE shipped as v8.14, and what version of Gitlab CI multi runner was current or shipped with Gitlab v8.14".
Have a new Tags sub page at the scope where I currently only see "All Projects | Shared Projects", in the Group tab of the Gitlab site, at say, http://gitlab.com/gitlab-org group it would look like this:
Currently I could do something like this manually with WIKIs, but I believe that this would add significant value to Enterprise Users and could become a piece of a future "hub" where understanding what Git versions went into various CI/CD deployments, or became stable versions, is maintained. If projects have a convention to always tag "release-8.0" exactly with that name, Gitlab could detect the same names, and be able to create these "Tags and group scope" automatically without me having to create the wiki page by hand, perhaps missing something that is in the gitlab site's same group but in a different repo and having a "release-8.0" tag just like the other bits did.
I think this is unlikely to be useful to ALL or most Gitlab CE users and so I logged this as an EE issue, but if you feel otherwise, feel free to move it.
Links / references
Will provide some if I find any. As far as I know this is my own unique idea, and it came to me when I was wondering "what ten git repos contain code that I shipped as Version 8, and what tags refer to those, and why isn't this easier and why isn't there a single source of truth for this, unless I manually make a wiki which might be wrong".
Alternative to the above could be using Submodules but I personally hate using submodules for this purpose. However maybe Git submodule workflows will improve.