Output
echo "Hello World
>
>
>
Abort the command by typing Ctrl + C simultaneously.
In this situation, you command line probably looks like one of these examples:
Output
echo "Hello World
>
>
>
Output
git commit -m "Add filename.txt
>
>
>
You can try one of the following solutions:
"
.As a first step, try going through the process again, whilst paying special attention to doing every step carefully. Oftentimes, there is some confusion when copying the SSH key to the clipboard or when entering a new passphrase, as there’s no visible feedback. After entering the command for copying the SSH key, you can usually trust that it is in your clipboard and move on to the next step. Similarly, be cautious what you are typing in as a passphrase, as you can’t see what you are entering. If you don’t want a passphrase, simply click enter twice when asked to set one up, leaving the passphrase empty.
Another issue could be that you have a pre-existing SSH key set up. You will get a warning about this and can simply use this pre-existing one to connect to your remote server of choice.
If none of these were the source of your issues, check out the GitHub SSH key troubleshooting documentation or the GitLab troubleshooting SSH site.
When authenticating with GitHub on macOS, you may notice that the password doesn’t show up in the command line as you type it. This is normal behavior to ensure security. You can still enter your password (or delete what you typed) even though it doesn’t appear on the screen. You can also copy and paste text, for example your PAT from GitHub. When authenticating on Windows, a new window might pop up in which you can enter your PAT.