SSH Existing Keys Callout

[kekoziar]

If an SSH key-pair exists, but can't be used or overwritten (perhaps one is attached to a school address, and they want to make a new key-pair for a personal account), a section should be added that explains how to do that.

[erinmgraham]

Thanks for the suggestion! The current docs already cover how to configure Git to use a non‑default SSH key-pair in response to PR #1091. Can you review this section, identify what information you need that is missing and propose some text?

…

________________________________ From: K.E. Koziar ***@***.***> Sent: Thursday, April 2, 2026 00:25 To: swcarpentry/git-novice ***@***.***> Cc: Subscribed ***@***.***> Subject: [swcarpentry/git-novice] SSH Existing Keys Callout (Issue #1115) This message was sent from someone external to JCU. Please do not click links or open attachments unless you recognise the source of this email and know the content is safe. [https://avatars.githubusercontent.com/u/28507641?s=20&v=4]kekoziar created an issue (swcarpentry/git-novice#1115)<#1115> If an SSH key-pair exists, but can't be used or overwritten (perhaps one is attached to a school address, and they want to make a new key-pair for a personal account), a section should be added that explains how to do that. — Reply to this email directly, view it on GitHub<#1115?email_source=notifications&email_token=AA5FFRLH2BT6LECY3SNDYKT4TURFTA5CNFSL4Z3JMQ5C6L3HNF2C22DVMIXUS43TOVSS6NBRHA3TGNBXGE4TDJTSMVQXG33OVJZXKYTTMNZGSYTFMSSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AA5FFRPTITBDQPXOUZTHTXT4TURFTAVCNFSM6AAAAACXJJAJCSVHI2DSMVQWIX3LMV43ASLTON2WKOZUGE4DOMZUG4YTSMI>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[kekoziar]

Thanks for giving me the keyword to look for. Here are some issues with that section.

• the section should be a callout, not a collapsed spoiler
  • the collapsed spoiler is formatted/designed to be preceded by a section callout (challenge, discussion, etc). It's less likely to be missed when uncollapsed or as part of a discussion/callout/etc tag.
  • the text in the section can be found using ctrl+f
  • on the AIO page, uncollapsing the section jumps the reader to the top of SSH Background and Setup (macos, chrome)
• the section title is a bit obscure. It should be something like, "Creating a second key" or "what if a key already exists"
• the section only addresses how to edit the config file with something that already exists
• the language should include the walkthrough steps for adding a second key

Solution
For All Options
Add a sentence after Since they don’t exist on Alfredo’s computer, he uses this command to create them. Ana has an existing SSH key pair associated with her university email, but wants to create a new SSH key pair associated with her personal email. The steps to create this are located in XYZ

XYZ Options

1. fix the AIO jumping behavior, keep in place
2. move (renamed) key conflicts section to the end of the SSH section, and uncollapse it
3. move (renamed) key conflicts section to the end of the SSH section and keep collapsed, but preface with minimal text in callout
4. move (renamed) key conflicts section to a challenge

This are just quick possible solutions. I'll work on the walkthrough and additional language.