Skip to content

Commit 254b3ba

Browse files
committed
Remove SSH-related changes from RStudio PR
1 parent aecc5fa commit 254b3ba

File tree

1 file changed

+0
-30
lines changed

1 file changed

+0
-30
lines changed

episodes/07-github.md

Lines changed: 0 additions & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -168,36 +168,6 @@ ls: cannot access '/c/Users/Alfredo/.ssh': No such file or directory
168168
If SSH has been set up on the computer you're using, the public and private key pairs will be listed. The file names are either `id_ed25519`/`id_ed25519.pub` or `id_rsa`/`id_rsa.pub` depending on how the key pairs were set up.
169169
Since they don't exist on Alfredo's computer, he uses this command to create them.
170170

171-
::::::::::::::::::::::::::::::::::::::::: spoiler
172-
173-
## Resolving SSH Key Conflicts: Custom Names and Paths
174-
175-
If you need to create an SSH key pair with a custom name or store it in a non-default location (e.g., because a default-named key like id_ed25519 already exists), Git may not automatically use it when pushing or pulling from GitHub.
176-
177-
One solution is to add a GitHub entry to your SSH config.
178-
179-
Open or create the SSH config file:
180-
181-
```bash
182-
183-
$ nano ~/.ssh/config
184-
```
185-
186-
Add an entry for GitHub, replacing the path with your key’s actual name and location:
187-
188-
```
189-
Host github.com
190-
HostName github.com
191-
User git
192-
IdentityFile ~/<full_path_to_SSH_key_file>/<key_name>
193-
IdentitiesOnly yes
194-
```
195-
196-
Save and exit. Now Git will use the correct key when pushing to GitHub.
197-
198-
::::::::::::::::::::::::::::::::::::::::::::::::::
199-
200-
201171
### 3\.1 Create an SSH key pair
202172

203173
To create an SSH key pair Alfredo uses this command, where the `-t` option specifies which type of algorithm to use and `-C` attaches a comment to the key (here, Alfredo's email):

0 commit comments

Comments
 (0)