Add SSH key file specification instructions #42110
Open
+56
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added instructions for manually specifying the SSH key file when connecting to GitHub, including example SSH command and expected output.
Why:
Closes: #42109
What's being changed (if available, include any code snippets, screenshots, or gifs):
Details have been added to advise a user to use the
-i <filename>command flag while troubleshooting the SSH connection in case they specified a non-default filename. For users that do specify a non-default filename, the SSH standard error (debug1: No more authentication methods to try; [email protected]: Permission denied (publickey).) is ambiguous and provides no guidance on what further troubleshooting steps to take. The edits to this article seek to address this gap.Check off the following: