This guide will walk you through creating a GitHub account, creating your "hub" repository for listing your labs, pulling the lab and creating new a file for assignments in that homework.
If you already have a personal GitHub account, feel free to use that -- no need to create a new one for this course. If you don't have an account, create one:
Head over to GitHub.com. Enter your choice of username, your school email address, and your choice of password. Click the big green "Sign up for GitHub" button. If prompted, choose the "free" plan.
Visit the IDD Hub example repository and "fork" it into your GitHub account by clicking the "fork" link; it should look similar to this:
For each lab, you'll need to make a pull request to get the new lab files into your hub. These are usually ready on Tuesday for the following Thursday.
From your Interactive-Lab-Hub, go to "Pull Requests".
Click on "New Pull Request".
Set the base repository to be your own Hub repo, and the head repository to FAR-LAB/Interactive-Lab-Hub. (This is not the default)
Click on “Create pull request“. If you cannot see the setting options, click on the "compare across forks".
Give description, e.g. "Updating new lab content".
Click on "Merge Pull Request."
-
Click the "Create new file" button on your repository page:
Note that you can also click the "Upload files" button instead to add images, movies, or other file times to your repository.
-
Give your new file a sensible name, like "exercise.py". The file extension you choose (".py" here) should match the programming language used in the file; for Python script use ".py"; for Javascript use ".js"; for Processing, use ".pde"; for Arduino, use ".ino".
Then, paste your code into the "Edit new file" tab.
Finally, click the "Commit new file" button.
-
To edit the main repository
README.md
file, or if you later wish to make changes to your code, you can do so through github as well. First, find the file you'd like to change, and click on the file name:Then, click the "Edit this file" icon:
Make your changes as in step 2 above.
THANKS TO JD ZAMFIRESCU FOR THE ORIGINAL GITHUB-GUIDE THAT THESE ARE RIPPED OFF FROM!