Merge pull request #19 from dlab-berkeley/sociologyquinn-patch-1

Add details about personal access tokens instead

Author: sociologyquinn

Reproducible Data Science/GitHub Intro.md

@@ -65,7 +65,7 @@ Then to make sure you only need to type in your password once, run the following
 git config --global credential.helper cache
 ```
 
-The next time you try to interact with a git repo from the command line (as we'll do momentarily), you'll be asked to type in your username and password. After doing this once, you shouldn't have to do so again.
+The next time you try to interact with a git repo from the command line (as we'll do momentarily), you'll be asked to type in your username and password. If you are prompted to set up a Personal Access Token (PAT), follow [these steps](https://docs.github.com/en/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token) to create one and enter the PAT instead of your password. Make sure you check off at least "repo" in step 8. Once you set this up, you shouldn't have to go through this process again. 
 
 ## Basic Workflow
 
@@ -202,4 +202,4 @@ Star the [D-Lab Computational Social Science Training Program repo](https://gith
 
 ![XKCD on Git](https://github.com/dlab-berkeley/Computational-Social-Science-Training-Program/blob/master/images/git%20xkcd.png) 
 
-Inevitably, especially as you get started, you are likely to run into errors. Usually these arise because of conflicts introduced during collaboration. You can mostly avoid these problems by making good use of branches and pull requests, or by reverting to the last point where you know things worked. We encourage you to do your best to resolve these kinds of problems directly and consult the instructors and/or stackexchange regularly. If you truly get stuck though, try downloading a fresh copy of the repo as a last resort.
+Inevitably, especially as you get started, you are likely to run into errors. Usually these arise because of conflicts introduced during collaboration. You can mostly avoid these problems by making good use of branches and pull requests, or by reverting to the last point where you know things worked. We encourage you to do your best to resolve these kinds of problems directly and consult the instructors and/or stackexchange regularly. If you truly get stuck though, try downloading a fresh copy of the repo as a last resort.