Add additional troubleshooting for non-standard SSH keyfile name

[kmanwar89]

Code of Conduct

• I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?

https://docs.github.com/en/authentication/troubleshooting-ssh/error-permission-denied-publickey

What changes are you suggesting?

This proposed edit is to include steps to specify the exact key filename as part of the ssh -vT git@github.com command while troubleshooting SSH connection issues. This resolves the issue of a user experiencing a git@github.com: Permission denied (publickey). error while following the linked troubleshooting article if they chose to use a non-default filename for their keyfile.

The expected outcome is a user will have clarity on how to specify the SSH keyfile while troubleshooting, preventing false-positive error messages that detract from the original troubleshooting flow.

I'll be opening a PR momentarily that links to this issue, per process.

Additional information

No response

[welcome]

Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.