Note that you will not be able to access the token string once you exit the window! You might want to keep this window open until you’ve completed the steps outlined next. It might be a good idea to temporarily paste the token into a plain text editor. When copying the token id, be careful not to add any empty spaces to the beginning or end of the token. This will allow you to read/write to your repo.Ĭlick Generate token at the bottom of the page.Ĭopy and temporarily save the token before closing the window. In this example, we’ll set it for 90 days.įrom the scopes menu, select repo. In the next field, you can set an expiration date for this token, or make it permanent. In the Note field, assign a name to this token such as the local computer you are creating this token for. In the left sidebar, click Personal access tokens.Ĭlick Generate new token (button near the upper left-hand side). On the left sidebar, click on Developer settings (this should be near the bottom of the left sidebar. Personal access token (PAT) based authenticationįirst, you need to follow these steps on GitHub:Ĭlick on your avatar (upper right-hand corner) and select Settings. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |