If you are configuring Git on your own computer, run the following code in the R console to ensure you have the required packages installed:
install.packages(c("usethis", "gitcreds", "gh"))
To ensure minimal challenges using Git during the class, we want to configure Git now with some default settings.
You only have to do this once per machine.
In order to track changes and attribute them to the correct user, we need to tell Git your name and email address. Run the following commands from the R console:
usethis::use_git_config(user.name = "Benjamin Soltoff", user.email = "firstname.lastname@example.org")
Benjamin Soltoff and
email@example.com with your name and email address. Your name could be your GitHub username, or your actual first and last name. Your email address must be the email address associated with your GitHub account.
In order to push changes to GitHub, you need to authenticate yourself. That is, you need to prove you are the owner of your GitHub account. When you log in to GitHub.com from your browser, you provide your username and password to prove your identity. But when you want to push and pull from your computer, you cannot use this method. Instead, you will prove your identity using one of two methods.
Cache credentials for SSH
The Secure Shell Protocol (SSH) is another method for authenticating your identity when communicating with GitHub. While a password can eventually be cracked with a brute force attack, SSH keys are nearly impossible to decipher by brute force alone. Generating a key pair provides you with two long strings of characters: a public and a private key. You can place the public key on any server (like GitHub), and then unlock it by connecting to it with a client that already has the private key (your computer or RStudio Serve). When the two match up, the system unlocks without the need for a password.
The URL for SSH remotes looks like
firstname.lastname@example.org:<OWNER>/<REPO>.git. Make sure you use this URL to clone a repository. If you accidentally use the HTTPS version, the operation will not work.
Create and store an SSH key pair
Run the following code in the R console:
You will be prompted to generate a new SSH key. Tell the computer “Yes”.
You will see a long string of characters in the console and be asked to open a browser now. Say yes, then copy and paste the public key (the whole line of text) into the resulting browser window. Give the key an informative title, something like
cfss-my-laptop, to record the class and computer. Click “Add SSH key”.
Cache credentials for HTTPS
With this method you will clone repositories using a regular HTTPS url like
https://github.com/<OWNER>/<REPO>.git. You will need a personal access token (PAT) and use that as your credential for HTTPS operations.
Get a PAT
Run this code from your R console:
This is a helper function that takes you to the web form to create a PAT. Use the pre-filled form and click “Generate token”. As the page says, you must store this token somewhere, because you’ll never be able to see it again, once you leave that page or close the window. For now, you can copy it to your clipboard (we will save it in the next step).
If you lose or forget your PAT, just generate a new one.
Store your PAT
In order to store your PAT so you don’t have to reenter it every time you interact with Git, we need to run the following code:
When prompted, paste your PAT into the console and press return. Your credential should now be saved on your computer.
Confirm your PAT is saved
Run the following code:
You should see output that provides information about your GitHub account.
Now that you have stored your PAT, you should not be asked to provide a username and password when you attempt to push to or pull from GitHub. It will just work! Hopefully.