Mod 0 Session 3 Readings and Responses

mod_0_session_3_readings.md

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.

GitHub is a web application that hosts Git repositories. GitHub allows to not only easily track project changes made by one user, but also record edits made by multiple users who collaborate in one project. Collaborative workflow looks like this:

1. A project is created on GitHub or on a local machine/commited/pushed up to GitHub;
2. Multiple users pull down the commits to their local computers, make a new commit, and start editing;
3. Multiple users commit changes throughout the editing process to track them;
4. Multiple users commit changes and push up their versions of the project to GitHub;
5. GitHub combines all versions together with tracked changes made by multiple users.

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

• Use the same format throughout a project among all collaborators
• Keep commit subject line clear and concise
• Capitalize the subject line and do not use period at the end of it
• Commit subject line uses imperative mood - A properly formed Git commit subject line should always be able to complete the following sentence: If applied, this commit will...
• Use the body of the commit message to concisely describe the change made.