Add hyperlink to 'New SSH key' in instructions

[mcfedr]

why are there no links in the docs? its so annoying

[github-actions]

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

• Spin up a codespace
• Set up a local development environment

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source	Review	Production	What Changed
authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md	fpt ghec ghes@ 3.21 3.20 3.19 3.18 3.17 3.16	fpt ghec ghes@ 3.21 3.20 3.19 3.18 3.17 3.16

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

[Copilot]

Pull request overview

This PR updates the “Adding a new SSH key to your GitHub account” instructions to include a direct hyperlink to the New SSH key settings page, making it easier for readers to navigate to the correct UI location.

Changes:

• Adds a direct link to the “New SSH key” page in the web UI steps.

[Sharra-writes]

@mcfedr I'm checking in about what Copilot is talking about with versioning. It may be why we don't have a link if it would need to be a different link depending on the version of the article.

[mcfedr]

@Sharra-writes its clearly not a very good PR to be honest - its probably somewhere in that include block is where to put the link - but its just super frustrating - and its throughtout the docs - no links to the actual pages - and its particurly because if you google 'add ssh key to github' or similar, you always end up on the docs pages, but its not where you wanna be

[Sharra-writes]

@mcfedr The rest of the team says we're not going to do this one, both because of the versioning problem and because our research says that too many inline links hurt the average user experience. That's why we tend to avoid them.