Git Clone Failed #113

New Issue

ejektaflex · 2023-09-16T23:43:24Z

ejektaflex commented

2023-09-16 23:43:24 +00:00

Following the instructions on the README.md, it says to do this:

git clone git@git.handmade.network:hmn/orca.git

This failed for me after connecting:

Using https://git.handmade.network/hmn/orca.git instead did work.

Following the instructions on the README.md, it says to do this: ``` git clone git@git.handmade.network:hmn/orca.git ``` This failed for me after connecting: ![image](/attachments/115a8d00-1371-405f-a794-dc0ddfe246d0) Using `https://git.handmade.network/hmn/orca.git` instead did work.

image.png

7.3 KiB

bvisness commented

2023-09-17 14:46:36 +00:00

Weird, I'd expect SSH to work with public repos. I'll have to look into that.

bvisness commented

2023-09-17 15:33:43 +00:00

Note to self: https://docs.gitea.com/help/faq#ssh-common-errors

bvisness commented

2023-09-17 15:40:59 +00:00

Ok, I guess it's simply that SSH access isn't allowed unless you add your public key to your Gitea profile. Obviously for the vast majority of our users this is not relevant. (This is the same as GitHub, it turns out, I just didn't realize because I've had a public key on my profile for so long.)

I will update the docs to use the HTTPS URL instead.

Ok, I guess it's simply that SSH access isn't allowed unless you add your public key to your Gitea profile. Obviously for the vast majority of our users this is not relevant. (This is the [same as GitHub](https://docs.github.com/en/get-started/getting-started-with-git/about-remote-repositories#cloning-with-ssh-urls), it turns out, I just didn't realize because I've had a public key on my profile for so long.) I will update the docs to use the HTTPS URL instead.

bvisness referenced a pull request that will close this issue

2023-09-17 15:43:14 +00:00

Use the HTTPS URL in the docs #120

bvisness self-assigned this 2023-09-17 15:45:31 +00:00

MartinFouilleul closed this issue

2023-09-17 15:59:35 +00:00

Sign in to join this conversation.