I know that what I am writing might not be helpful to the OP but I still write it in hope that it will help in clarifying someone's confusion or maybe mine in the future.
Cloning with HTTPS URLs
The https://
clone URLs are available on all repositories, regardless of the public or private repo. https://
clone URLs work even if you are behind a firewall or proxy.
When you git clone, git fetch, git pull, or git push
to a private remote repository using HTTPS URLs on the command line and git fetch, git pull or git push
to a public remote repository, Git will ask for your GitHub username and password. When Git prompts you for your password, enter your personal access token (PAT) instead. Password-based authentication for Git has been removed. see "Creating a personal access token"
You can save these username and password(PAT) in your repo/.git/config
to make it not ask everytime. see this StackOverflow answer
Cloning with SSH URLs
To use these URLs, you must generate an SSH keypair on your computer and add the public key to your account on GitHub.com.
When you git clone, git fetch, git pull, or git push
to a remote repository using SSH URLs, you'll be prompted for a password and must provide your SSH key passphrase. But if you set no passphrase in the first place then it won't ask you.
See this StackOverflow answer if your ssh-agent continues to annoy you by asking passphrases every time you do push pull
.
Although most of the content is sourced from github-docs but it has a mistake you can see if you try to find change