Your one-stop-cake-shop for everything Freshly Baked has to offer

docs: always use https to clone #2

merged opened by a.starrysky.fyi targeting main from private/minion/push-wousukrwqsyz

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

Labels

None yet.

requested-reviewers

None yet.

approved

None yet.

tested-working

None yet.

rejected

None yet.

assignee

None yet.

Participants 1
AT URI
at://did:plc:uuyqs6y3pwtbteet4swt5i5y/sh.tangled.repo.pull/3lyqrqtkl2d22
+6 -4
Diff #0
+6 -4
README.md
··· 36 36 ForwardAgent yes 37 37 ``` 38 38 39 - When you've added this section to your ssh config, you can clone over SSH. 40 - Except for when creating branches, pushing will work as-normal for SSH clones. 39 + When you've added this section to your ssh config, you can add a custom push URL 40 + to use SSH. 41 41 42 42 ```bash 43 - git clone ssh://git@git.freshlybakedca.ke/patisserie.git:/packetmix.git 44 - # Swap out "packetmix" at the end of the URL for whatever project you want to clone 43 + git remote set-url --push ssh://git@git.freshlybakedca.ke/patisserie.git:/packetmix.git 44 + # Swap out "packetmix" at the end of the URL for whatever project you have cloned 45 45 ``` 46 46 47 + Except for when creating branches, pushing will work as-normal for SSH clones. 48 + 47 49 ### Creating new branches 48 50 49 51 When pushing to *josh*, creating branches won't work on a regular `git push`.

History

1 round 0 comments
sign up or login to add to the discussion
a.starrysky.fyi submitted #0
1 commit
expand
docs: always use https to clone
expand 0 comments
pull request successfully merged