Expand URL Schemes for Release assets beyonf http(s) and ftp
Problem to solve
When adding Release assets to a release, you can specify URL and title. Currently (at least for the GUI), "URL must start with http://, https://, or ftp://" which shouldn't be a restriction because you can define custom URI-Schemes (see https://msdn.microsoft.com/en-us/library/aa767914(v=vs.85).aspx) which cannot be specified here.
Intended users
User experience goal
If a company like ours is developing a windows application, every release will be placed somewhere on a (shared) fileserver. When you have a registered URI Scheme (see above, basically you add a few entries to the registry so yourapplication:.... hyperlinks in the browser will be opened with this application), you could open the application ("the release") directly from the Release Page in gitlab, which would be awesome.
Proposal
My suggestion is to make this a warning only (so people don't forget https:// before the URL).
It might be OK to throw an error if the link does not contain a :, which is contained in every URI Scheme.
Documentation
Not necessary?
What does success look like, and how can we measure that?
Try to input yourapplication:run in the release asset URL and save.
What is the type of buyer?
Every Windows-Developer who compiles release artifacts into executable files (i.e. .NET, C++, JAVA, ...)