Skip to content

Instantly share code, notes, and snippets.

Show Gist options
  • Select an option

  • Save edwindelbosque/2f33bd8204d7b4761456eb5264c75b3f to your computer and use it in GitHub Desktop.

Select an option

Save edwindelbosque/2f33bd8204d7b4761456eb5264c75b3f to your computer and use it in GitHub Desktop.
Mod 0 Session 4 Readings and Responses

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 git flow was hard at first to wrap my head around, but once you practice it, it just clicks and becomes so easy to understand:

  1. I will be working on brand new file that I created locally in my laptop.
  2. I think of tracking the changes I do in this file and so I "git init" to create a local repo.
  3. I git add file.txt in order to start tracking the file in my system.
  4. I keep on finishing my code and decide that it looks good enough, so I once again git add and git commit -m "Initial commit" to finalize the edits.
  5. I will then git push the file into the remote repository, which is GitHub so my teammates can see it and review it.
  6. Someone in my team will fork my repo and then clone it into their local repository.
  7. Then they can open their text editor and review and make changes as they see it fit.
  8. When they have finished reviewing my code, then they will git add file.txt and then proceed to git commit -m "Modify A"
  9. Then they will git push the file into GitHub once again.
  10. They will then perhaps do a pull request to merge their changes into my main repo.
  11. I review everything is correct and then I approve the pull request.

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

  • Classs: "screen"

  • Objects: "tv", "monitor", "laptop", "phone", "ereader", "watch"

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/edwindelbosque/69202bb38528c5767eb7ef7c2efbd7a7

@katiescruggs
Copy link

Nice work, @edwindelbosque! I appreciate the quote about git you included in your gist -- hadn't heard that one before!

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