From 26a238c28669efbab9f396a24f1d2ddf61c72215 Mon Sep 17 00:00:00 2001 From: Skyler Grey Date: Sat, 13 Sep 2025 21:59:53 +0000 Subject: [PATCH] docs: always use https to clone Change-Id: wousukrwqsyzvzsmsvtysovmvklloytu Josh doesn't seem to be working correctly with cloning over SSH, but we know it works for pushing. Therefore, we should mention git's support for having a different push URL and recommend always cloning over HTTPS --- README.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 8b9b3b9..145a880 100644 --- a/README.md +++ b/README.md @@ -36,14 +36,16 @@ Host git.freshlybakedca.ke ForwardAgent yes ``` -When you've added this section to your ssh config, you can clone over SSH. -Except for when creating branches, pushing will work as-normal for SSH clones. +When you've added this section to your ssh config, you can add a custom push URL +to use SSH. ```bash -git clone ssh://git@git.freshlybakedca.ke/patisserie.git:/packetmix.git -# Swap out "packetmix" at the end of the URL for whatever project you want to clone +git remote set-url --push ssh://git@git.freshlybakedca.ke/patisserie.git:/packetmix.git +# Swap out "packetmix" at the end of the URL for whatever project you have cloned ``` +Except for when creating branches, pushing will work as-normal for SSH clones. + ### Creating new branches When pushing to *josh*, creating branches won't work on a regular `git push`. -- 2.43.0