Support additional clone schemes

[rdwz]

Feature Description

the custom handler for VSCodium is
vscodium://vscode.git/clone?url=

Screenshots

[jolheiser]

This makes me think we should somehow make this configurable.

One option is to maintain a custom template, but understandably that's less than ideal for this.
Another option is to somehow make this a type of config setting that's dynamic.

Nothing against vscodium, if I'm honest I also (personal opinion) don't like that we've already added a vscode link to begin with.

Perhaps we should discuss how to make this generic before we end up with another "adding webhooks for every service" problem. 😅

[6543]

User preverences ...

[silverwind]

Does VSCodium not support vscode:// urls? I think it'd be better to start there. Maybe there is also a editor-agnostic scheme we could use.

[jolheiser]

I think we could

1. Add another custom-only template like how we do for header links, etc. (to limit breakage) or;
2. Somehow make this a dynamic configuration option similar to external renderers

[silverwind]

No custom templates please, they suck 😉. Maybe with config:

repo.ADDITIONAL_CLONE_SCHEMES = vscodium://,sublime://

Still, generall I think the issue is on the editors, not us.

[jolheiser]

Still, generally I think the issue is on the editors, not us.

Probably true, but a custom protocol probably lets them do other things that's specific to each editor (maybe?)
I think a config option would work fine with a little forethought

[silverwind]

Problem with the config approach is user can not set icon, but that may be acceptable.

[silverwind]

Well I suppose one could have a JSON value in the config option, but I don't think we do those yet.

repo.ADDITIONAL_CLONE_SCHEMES = '[{"scheme": "vscodium://", "icon": "<svg/>"}]'

[jolheiser]

Could have a config option for local image or web image.
In terms of "security", since it would be config-level, it would be up to the admin?

[silverwind]

Would keep it simple, just SVG string support. Security should be fine as it's in the config, only admin-accessible.

[jolheiser]

Would keep it simple, just SVG string support.

For a web image, technically Gitea could even host the image in its custom dir, which would still allow users to serve it themselves without relying on another service.
And I think might be nicer than storing JSON in an ini config?