Turning in Assignments

Overview

We will use git to turn in assignments.

I will send a link via Canvas for each assignment. The link will ask you to logon to GitHub and join the BIS180L classroom. I can demo this during class if needed.

For each assignment click on the link and follow instructions to create your own repository for the assignment.

Clone the repository to your Jetstream2 instance.

cd into the repository on your instance.

Get to work!

Remember to git add files that you create or change, git commit your changes and git push. DO THIS VERY OFTEN! That way if something goes wrong you won’t have lost any work.

Make your final pushes before the assignment due date.

You can check your repo on GitHub.com to make sure that your latest changes have been uploaded.

Turning in Assignment 1

Assignment 1 is due Tuesday 4/11 at 1:00 pm. But you can go ahead and do these steps now and update later.

  1. Open the assignment link
  2. Logon to GitHub if necessary. Wait for the verification email if necessary and enter your verification code.
  3. Refresh your browser page until your repository shows.
  4. Click on the “Code” button, select SSH and copy the URL.
  5. Clone the repository to your Jetstream2 instance.
  6. cd into the repository.
  7. mv the assignment 1 files into the repository. These are:
    1. Notebook from Unix Tutorial (unix_notes.md)
    2. Answers to Unix Tutorial exercises (May be part of file 1 or separate)
    3. The markdown biography from the end of the Markdown lab
    4. Your notes from the git tutorial/lab (gitNotes.md)
  8. Use git add plus the filenames to stage your changes.
  9. Use git commit -m to add your changes.
  10. Use git push to push your changes to GitHub.
  11. Use Rstudio (or nano or the editor of your choice) to edit the README.md file in the repository to add the URL for your shared weekend plans repository. Be sure to use Markdown format to create a clickable link.
  12. Add, commit, and push your changes to the README.md file.
  13. Use your web browser to look at the repository on GitHub.com to make sure that your changes were pushed.