### Code of Conduct - [x] I have read and agree to the GitHub Docs project's [Code of Conduct](https://github.com/github/docs/blob/main/.github/CODE_OF_CONDUCT.md) ### 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_