Skip to content

Instantly share code, notes, and snippets.

@RayRedGoose

RayRedGoose/mod_0_session_4_readings.md

Forked from rwarbelow/mod_0_session_4_readings.md
Last active July 9, 2019 20:00
Show Gist options
  • Save RayRedGoose/ec9d2d6560ec69208bc267da4f27e967 to your computer and use it in GitHub Desktop.
Save RayRedGoose/ec9d2d6560ec69208bc267da4f27e967 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.

1. Initialize the central repository (As repo owner)

Someone needs to initialize a Git repository.

2. Hosted the central repository (As repo owner)

The central repository is often created through 3rd party Git hosting services like GitHub.

3. Fork the central repository (As contributor)

Fork the central repository to contributor's remote repository. A fork is a copy of a repository that contributor manage. Forks let contributor make changes to a project without affecting the original repository.

4. Clone the central repository (As contributor)

Clone the forked central repository from developer's own remote repository. Each developer creates a local copy of the entire project. This is accomplished via the git clone command.

5. Create a branch

It is always good practice to create a branch from the project so that developer can leave the "master" branch in tact while developer add new content or functionality.

6. Make some changes & commits

A developer can make changes using the standard Git commit process: edit, stage, and commit.

7. Push new branch with commits to developer's remote repos (As contributor)

Developers add new commits to their own remote repository.

8. Make a pull request (As contributor)

Developer make a pull request to ask the project owner to review a contribution and to merge the pull request. Developer will have to comment on the pull request before submitting his pull request.

9. Review the pull request (As repo owner)

Project owner review the pull request, comment on the pull request, and provide feedback. If it looks good, then project owner merge 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.):

  • Class: Cake

  • Objects: Red_velvet, Tiramisu, Cheesecake, Brownie.

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:

Beginners Guide to Git by Raisa Primerova

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