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.

The first step is to create a branch in your project that is seperate from the master branch. This allows you to try new ideas and make changes without affecting the main branch. The changes wont be merged until its ready to be reviewed by someone you're working on the project with. Whenever you make changes to your branch it is called a commit. Commits make it easier for the people youre working with to follow the changes youve made and why they were made. Each commit is a seperate change which allows the change to be deleted easily if something goes wrong or needs further changing. Next you want to make pull requests to start discussions with your collaborators about your commits. These can be made at any time to create a discussion about what youre currently working on. They can always see what changes would be implemented if they accept you request. Next you can deploy from your branch for testing in production before merging it with the master branch. After the pull request has been reviewed and it passes your tests, you can deploy the changes to verify them in production. After the changes have been verified in production, you can finally merge your code into the master branch.

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.):

car: sedan, suv, mini-van, truck

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/SamuelColeman/88e7752e71958e9c026e3b084792ae56