Session 2 HW

CAREFULLY READ ALL THE INSTRUCTIONS BEFORE STARTING THESE EXERCISES!

To start this assignment:

1. Click the button in the upper right-hand corner that says Fork. This is now your copy of the 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.

Readings + Responses

Git Commit Messages (17 min)

Read this article on git commit messages

• Your key take-aways OR how you're going to implement specific points (minimum 2):

• Reduce get messages as much as possible while maintaining the information you are trying to get accross.
• Long term success of a project is helped a ton by descriptive, concise git messages.
• If there is significant changes that need to be explained use a short subject line followed by a blank line and then a more in depth discussion in the body of the message.

What's the use of the staging area in git? on Stackoverflow (15 min)

The idea of the staging area is frequently one of the trickiest concepts to wrap your head around when you're first learning git. Read the question and answers (or do your own Googling on the git staging area). Then, create your OWN metaphor comparing the staging area to something in real life.

• Type your metaphor below:

When writing a paper it's important to have multiple drafts. However you do not need a new draft if you were to just work on one paragraph or one sentance. Staging allows coders to make the size of updates that the project needs. Sometimes that is a whole new draft, sometimes it's a new paragraph and other times it's just a modified sentance. Staging allows the flexibility to commit the changes that need to be made in a way like working on a paper.

Exercises

1. Git Practice (15 min)

Follow the steps below to practice the git workflow. Be ready to copy-paste your terminal output as confirmation of your practice.

1. Create a directory called git_homework. Inside of there, create a file called thoughts.md
2. Initialize the directory
3. Use git status to ensure you are set up for tracking using Git
4. Add your thoughts.md to the staging area
5. Check the git status
6. Create an initial commit (Note: Be sure to follow the correct message format for your first commit!)
7. Check the git status
8. Add two takeaways you've had from your first few classes of Mod 0 as it relates to success at Turing.
9. Check the git status
10. Check the changes you've made using git diff
11. Add the changes to the staging area
12. Commit the new changes (Note: Be sure to follow convention for commit messages!)
13. Check the status
14. Add two new strategies you are committed to trying during the rest of Mod 0 to thoughts.md
15. Add the changes to the staging area
16. Commit the new changes (Note: Be sure to follow convention for commit messages!)
17. Add at least one shoutout to someone who has helped you, supported you, or just been a positive presence in the last two weeks!
18. Add the changes to the staging area
19. Commit the new changes (Note: Be sure to follow convention for commit messages!)
20. Show the log of your work in oneline format using git log (This will likely require some Googling)

Copy and paste all of the terminal text from this process below (not just the history):

/Users/conorbarthel/turing/0module  $mkdir git_homework
/Users/conorbarthel/turing/0module  $cd git_homework
/Users/conorbarthel/turing/0module/git_homework  $touch thoughts.md
/Users/conorbarthel/turing/0module/git_homework  $git status
fatal: not a git repository (or any of the parent directories): .git
/Users/conorbarthel/turing/0module/git_homework  $git init
Initialized empty Git repository in /Users/conorbarthel/turing/0module/git_homework/.git/
/Users/conorbarthel/turing/0module/git_homework main $git add git_homework
fatal: pathspec 'git_homework' did not match any files
/Users/conorbarthel/turing/0module/git_homework main $git add thoughts.md  
/Users/conorbarthel/turing/0module/git_homework main $git status
On branch main

No commits yet

Changes to be committed:
  (use "git rm --cached <file>..." to unstage)
	new file:   thoughts.md

/Users/conorbarthel/turing/0module/git_homework main $git commit -m "initial commit"
[main (root-commit) 3325244] initial commit
 1 file changed, 0 insertions(+), 0 deletions(-)
 create mode 100644 thoughts.md
/Users/conorbarthel/turing/0module/git_homework main $git status
On branch main
nothing to commit, working tree clean
/Users/conorbarthel/turing/0module/git_homework main $follow directions carefully and come to class prepared 
zsh: command not found: follow
/Users/conorbarthel/turing/0module/git_homework main $git status
On branch main
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
	modified:   thoughts.md

no changes added to commit (use "git add" and/or "git commit -a")
/Users/conorbarthel/turing/0module/git_homework main $git diff
diff --git a/thoughts.md b/thoughts.md
index e69de29..f08d56c 100644
--- a/thoughts.md
+++ b/thoughts.md
@@ -0,0 +1,2 @@
+Read directions carefully
+Come to class prepared
/Users/conorbarthel/turing/0module/git_homework main $git add thoughts.md
/Users/conorbarthel/turing/0module/git_homework main $git status
On branch main
Changes to be committed:
  (use "git restore --staged <file>..." to unstage)
	modified:   thoughts.md

/Users/conorbarthel/turing/0module/git_homework main $git commit -m "Add two lines"   
[main 8e7f712] Add two lines
 1 file changed, 2 insertions(+)
/Users/conorbarthel/turing/0module/git_homework main $git status
On branch main
nothing to commit, working tree clean
/Users/conorbarthel/turing/0module/git_homework main $git add thoughts.md
/Users/conorbarthel/turing/0module/git_homework main $git commit -m "Add two strategies"
[main 128e6a1] Add two strategies
 1 file changed, 2 insertions(+)
/Users/conorbarthel/turing/0module/git_homework main $git add thoughts.md
/Users/conorbarthel/turing/0module/git_homework main $git commit -m "Add shoutout"
[main d9f87f4] Add shoutout
 1 file changed, 1 insertion(+)
/Users/conorbarthel/turing/0module/git_homework main $git log --pretty=oneline
d9f87f4ea6d6da256b2f0839ea14c84cc6a04e16 (HEAD -> main) Add shoutout
128e6a1c36065839c835ee8ec9c180530cc117d5 Add two strategies
8e7f7127d045e9ea52001fdf056d927da1dac72c Add two lines
3325244256f861b716b77304f99d3abb6d7e224c initial commit
/Users/conorbarthel/turing/0module/git_homework main $

IMPORTANT: Do NOT remove this git_homework directory. You will be using this directory during the next session.

2. Markdown Practice (20 min)

Your task: create a "Plan for Mod 0" documenting your gameplan for success in Mod 0, using Markdown.

Markdown (.md) is the format all of your homework gists are written in.

Using this markdown cheatsheet, create a new gist of your own by clicking the New Gist button in the upper right-hand corner of the screen.

Also, images can be a little tricky in gists and Github - be sure to check out the drag-n-drop shortcut from the first answer on this Stack Overflow post!

In the box to title your Gist, be sure to use follow this format: firstName_lastName_mod_0_plan.md

NOTE: Remember to add a .md file extension to filename of your new Gist. Otherwise it will not register as markdown.

In addition to documenting your gameplan for success in Mod 0, 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 (in Javascript for Frontend or in Ruby for Backend)
• at least one inline code block (greyed text)
• at least one image
• ⚡️ https://gist.github.com/conorbarthel/3a44dc57a6e723748f3e9d98897099b5 ⚡️

Self Assess

Using the rubric below, assess how you did with these exercises. These are the same metrics your instructors will use to determine if you are prepared for Mod 1!

• I read carefully read ALL directions
• I completed all parts of the exercises (not including Extensions) to the best of my ability
• I used correct syntax, spacing and naming conventions
• I followed ALL formatting instructions
• I pushed myself out of my comfort zone and experimented/broke things to try to learn
• I spent no longer than 20-30 mins Googling a specific problem before asking for help
• I went back to the lesson to search for clarification before asking for help

Questions/Comments/Confusions

If you have any questions, comments, or confusions that you would like an instructor to address, list them below:

Stuck? Having Issues?

Are you stuck on something? Here is the BEST way to ask for help:

• Start or reply in the thread with the problem you are facing. Be sure to follow the guidelines for asking questions below:
  • I can explain what I am trying to do or accomplish
  • I can what I have tried so far and/or what resources I've tried online
  • I can describe specifically what I am stuck on
  • I provided screenshots and/or code examples to give context
    • If I provided short code examples, I used inline code formatting for single lines of code/error messages
    • If I provided larger blocks of code, I used a code snippet in the correct format (such as .js or .rb)
• Usually, your classmates will be able to answer your question or point you in the right direction very quickly! If not, an instructor will reply within 24-48 hours