Gusted
Ready for review... I'm not sure how to handle the UI to display the long ssh key.
Force-pushed twice, because git was being funny.
@silverwind Could you give some input for the UI? I've tried some designs now in order to display the Public SSH Key, but I haven't been able show it nicely...
I'm not able to get any kind of neat and clean UI while still showing the public key. Changed it to be behind a copy button(updated PR message with updated...
> Assume users have 100 push mirrors, then he has to add 100 public keys in target forge website? Well if the user is going to create multiple push mirrors...
Fixed up conflicts and also accidentally pushed some code in that commit to actually be able to parse `[email protected]:gitea/gitea` URLs(which was somehow still in a stash).
> One question: What if the remote only supports RSA key If some Forge only support some older type of Public-key cryptography, then I'm happy to hear about it and...
> 7\. Because this error appears: Where am I supposed to enter the SSH key? Or does Gitea automatically take one of my verified keys? Or how is that handled?...
@delvh https://github.com/go-gitea/gitea/pull/18835/commits/86fec2defe312aa21d3f3cbe8075e41a34f28802 should fix your panic, I had LFS disabled.
> Do we want to display this warning? Yes, but we might want to trim the `Warning: Github.com has been added ...` path. IIRC this error popup was explicitly added...