-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support additional clone schemes #21121
Comments
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. 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. 😅 |
User preverences ... |
Does VSCodium not support |
I think we could
|
No custom templates please, they suck 😉. Maybe with config:
Still, generall 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?) |
Problem with the config approach is user can not set icon, but that may be acceptable. |
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/>"}]' |
Could have a config option for local image or web image. |
Would keep it simple, just SVG string support. Security should be fine as it's in the config, only admin-accessible. |
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. |
hey @author @redwerkz can u add a test link in the description (first comment) of this issue? e.g.: "Repositories for trial on gitea are at: https://try.gitea.io/" |
Please don't talk about your opinion of community governance in a special issue. |
Feature Description
the custom handler for VSCodium is
vscodium://vscode.git/clone?url=
Screenshots
The text was updated successfully, but these errors were encountered: