Skip to content

Instantly share code, notes, and snippets.

@adamsjr8576

adamsjr8576/mod_0_session_4_readings.md

Forked from rwarbelow/mod_0_session_4_readings.md
Last active July 9, 2019 22:45
Show Gist options
  • Save adamsjr8576/29d177c2d960ee747342b6796f5879ec to your computer and use it in GitHub Desktop.
Save adamsjr8576/29d177c2d960ee747342b6796f5879ec to your computer and use it in GitHub Desktop.
Download ZIP
Mod 0 Session 4 Readings and Responses
Raw
mod_0_session_4_readings.md

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.

  • A general process of a collaborative git workflow using Github begins with the creation of a project (folder and file for example) coupled with the creation of a repository on Github. One the project is made and it has been added and committed to a git repository the initial creator can then connect and push the repository to the repository made in Github. Once the repository on Github has been made (this would be the origin or source file) and updated with the project then it can be accessed by other people, as long as it is made public or other users are granted access. The second user attempting to edit the repository will select the clone button on the project in Github (they might have to fork the repository first) and then use the url provided for that to clone the repository in git - this would be their initial pull. At this point the user can move into the folder and files to edit on their device. They will then make edits and commits on their local repository, and once they are done or want to update the origin then they will push their local changes back to Github. At this point you can create a pull request on Github and the owner (your boss or co-worker) can review your edits and changes before merging them to the origin. accurately and consistently labeling your commits helps a lot with this review process. Once confirmed then the changes can be merged with the origin and your work has succesfully been applied to the origin. Now, if someone else pulls the repository down to work on, your changes will be reflected in that. This way multiple people can be working on the same repository at the same time via the pull and push methods.

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

  • "footwear" class

  • objects: "shoe", "sandal", "flip_flop", "slip_on", "ski_boot", 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/adamsjr8576/f911dfde5e875188f5d846364c74e422

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment