If jdcolby clones that same repo1 repository from her GitHub account using SSH, she would type: $ git clone on setting up authentication using both techniques follow. If you use an SSH key, you will connect to your GitHub repo over SSH.įor example, if jdcolby clones repo1 from her GitHub account using HTTPS, she would type: $ git clone If you use PAT, you will connect to your repo over HTTPS–this is the connection used in this workshop.

Note that your choice of authentication will be dictated by the way you connect to your GitHub repo. Both techniques require some degree of configuration on both your GitHub account and your local machine, but the PAT will be the easiest to set up for your students. Two of these options are covered here: Personal Access Token ( PAT) or SSH-based authentication. Instead, you need to adopt one of several authentication options. Using your GitHub password is no longer allowed after August 13, 2021. For example, when pushing changes made in a local repo to GitHub, the session would look something like this: $ git push Prior to August 13, 2021, you were allowed to authenticate by typing a username and password every time you pushed or pulled from GitHub.

Avoiding the need to enter a passphrase.

Converting an existing HTTPS local repo to SSH.

Adding the SSH key to the ssh-agent process.

Personal access token (PAT) based authentication.

Git windows authentication