Guide to GitHub Classrooms

For this course, you will be submitting your lab work to a GitHub repository and submitting a link to your work to the corresponding Dropbox on Pilot. The guide below will help you with setting up the repository you will be required to use for this course - it is a private repository with permissions set in order to protect your work and share it with only myself and the TAs and contains some default content to get started.

• Quick Start
• Use GitHub Repo in VSCode
• Setup SSH Authentication
• Using your Repository
• Troubleshooting

Quick Start:

1. Create / have a GitHub account
   • Sign up
2. Take the Pilot Quiz to collect your WSU email and GitHub username
   • If you joined the course late, contact instructor immediately to get correct setup
3. Receive an invitation to your course repository
   • Invite will go to account linked to your wright.edu email
   • URL will be in form: https://github.com/WSU-kduncan/ceg2350-lastnamenum-f26
   • Repo is inherently private and only visible to instructors, TAs, and yourself
4. Have git installed on the system you are working with
   • git download page
   • With winget package manager for Windows: winget install --id Git.Git -e
   • With apt package manager for Linux: sudo apt install git

Use GitHub Repo in VSCode

See Instructions in Lab 01

Setup SSH Authentication

1. Generate a new SSH key with the command:
   • ssh-keygen -t ed25519 -C "your_email@example.com"
   • Hit enter to use the default storage location and name
   • Hit enter to skip entering a passphrase
   • NOTE You need to create a key pair on each system you want to use.
   • AWS Ubuntu system = 1 key pair
   • Your system = 1 key pair
   • A system at wright state = 1 key pair
2. Go to the folder where the key pair was saved. Look for the file that ends with .pub
3. Open the file, and copy its contents
4. Add your public key to GitHub
   • Go to “Settings” - “SSH and GPG keys”, then select “Add new key”
   • Give your key a useful name that ids which computer it belongs to
   • Paste the contents of the .pub file in the box
5. To clone the repository:
   • Click the green Code button
   • Select SSH for SSH key authentication
   • In a terminal use git clone followed by the corresponding URL to clone your repository

Using your Repository

You now have a repository on GitHub, and have added to your GitHub account a public key associated with a private key protected by you.

This will be discussed in class and lab, but as a cliff notes version, your next steps are to:

• clone your repository locally (to the machine you are using)
  • Remember to clone your repository to each device you want to work with it on. Yup, that also means a key pair for each
• add new files for tracking, or add files that have had changes made to be committed
• commit your changes, along with a commit message that states what has changed
• push your commit(s) to GitHub
• Refresh your repository on GitHub in your browser to prove it pushed (seeing is believing)
• status will output some hints about what is going on and what may need to happen next

Troubleshooting

Q. I lost my SSH key (computer died, data deleted, etc), what now?
A. Your GitHub repository is fine. It’s in “the cloud” (add sparkles and rainbows).
Follow the steps in SSH Authentication to generate a new key pair for use with your GitHub account.

Q. It’s asking for a passpharase?
A. In the event that you are asked for a passphrase, you created one when making your SSH key. There is no undo button.
Follow the steps in SSH Authentication to generate a new key pair (and don’t put a passphrase this time)
for use with your GitHub account.