Session 4 Readings and Responses

The readings and responses listed here should take you approximately 50 minutes total.

To start this assignment:

1. Click the button in the upper right-hand corner that says Fork. This is now your copy of this document.
2. Click the Edit button when you're ready to start adding your answers.
3. To save your work, click the green button in the bottom right-hand corner. You can always come back and re-edit your gist.

Assignment 1 (30 min)

Read Turing Instructor David Whitaker's article on Git and GitHub

• Use the article and outside resources (Google!) to describe the general process of a collaborative git workflow in the space below.

    With GitHub and Git - users can upload versions of a project in intervals called commits to 
    folders called repositories that can be viewed and accessed by multiple people through GitHub
    
    Repositories can be hosted online on GitHub 
    
    You can create repository on GitHub - gives you instructions to work with terminal to connect repo (cannot be empty -         must have done git init, add, and commit. ) 
    GitHub provides URL - in terminal you enter "git remote add origin <URL>"
    then enter "git push -u origin master"
    follow order :  "git push <remote_name> <branch_name>"
    
    If cloning from another repository on GitHub - location is callec origin 
    (URL where it is hosted on GitHub) : 
    From original repository you can fork (to create a copy on GitHub) or clone (to clone to your
    computer (local)
    Must be forked to clone
    When you clone you do not need to do Git Init
    Once you clone the repository you can edit and make changes at the local level. You can add and
    commit these changes as usual and push them to the original on GitHub. If you have collaborator 
    rights your changes can push immediately.         
    If you are not a collaborator it will push to your local copy on GitHub - changes can be 
    reviewed by collaborators for inclusion in the original repo. 
             (create pull request on base branch - push your local commits to pull request - 
             collaborators can review, add comments, add commits to pull request - if proposed
             changes are accepted you can merge pull request to base branch)
    
    The general cycle is to pull down repo's - edit - push changes back to GitHub- pull it down with
    new updates from others - edit - push back- etc (using Git to do so)
    
    GitHub has other helpful tools such as Issues - so bugs and udpates can be tracked
    
    Can also delete a branch, rename a branch, and push tags using Git push 
    (Unsure how to differentiate between tag name and branch name?)
  

Assignment 2 (10 min)

• Watch Tim's video on classes and objects.

• In the space below, come up with your own example of a class (like "bottle") and several objects (like "spray bottle", "nalgene", etc.):

          class Footwear : 
                       Instances : ["sneaker", "sandal", "dress_shoe", "heels", "wedges",etc]
  

Assignment 3 (60 min)

Skim this intro to Markdown. It's not necessary to memorize because you can always come back to it as a reference.

Next, create a new gist of your own by clicking the New Gist button in the upper right-hand corner of the screen. Create a "Beginners Guide to Git" documenting your git knowledge so far using Markdown. Incorporate each of the following features into your Gist:

• at least two headings of different sizes

• at least one numbered list

• at least one bullet point list

• at least one bold word/phrase

• at least one italic word/phrase

• at least one code block

• at least one inline code block (greyed text)

• at least one image

• Paste the link to your gist here:

https://gist.github.com/mcat56/20c9ea2f613aaa46d53e77f98df10116