Skip to content

Instantly share code, notes, and snippets.

@brycemara
Forked from damwhit/mod_0_session_3_readings.md
Last active July 22, 2020 21:12
Show Gist options
  • Save brycemara/709f613179f974dff55325540b8701ee to your computer and use it in GitHub Desktop.
Save brycemara/709f613179f974dff55325540b8701ee to your computer and use it in GitHub Desktop.
Mod 0 Session 3 Readings and Responses

Session 3 Readings and Responses

The readings and responses listed here should take you approximately 35 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 (20 min)

Read David'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 process begins with one person or team working on a specific document(code, blog, term paper, etc.). I would then access the doc by pulling it from GitHub or creating my own document and begin my edits. After I'm happy with my edits I would then push them back to GitHub to be published publically so the rest of the team could see my edits. They can also be working on this document at the same time and editing it themselves. GitHub will show all edits and who did what, you can keep pulling and pushing different versions of this document until you get to a final draft. But even then you can see all your changes, additions and deletions. I think of GitHub like GoogleDocs on stereoids. And also a lot easier to handle larger projects and multiple edits.

Assignment 2 (17 min)

Read this article on git commit messages

  • Your key take-aways OR how you're going to implement specific points (minimum 2):
  • A big take away was to be more thoughtful when using my git commit -m "Messages here". It's easy to become lazy and careless with these which will only be more confusing to me further down the road. I'm going to try to use git log more often to be more aware of what I am putting in my git commits.
  • A part of being more thoughtful with my commits will be to go through the seven steps and apply each to my commits. Also focusing on using the body to explain the what & why instead of how it was done. This will only be done my practicing with the command line and commit messages.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment