repeater_fam_hw2.md

Repeater Fam HW 2

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

Review this article on git commit messages, especially the section on the 7 Rules of Great Commit Messages

Reflections

What has been one "win" you've had during your repeat of Mod 0?

What is one challenge you've faced in your repeat of Mod 0?

Exercises

1. Git Practice (15 min)

We will be using the below git worklfow as part of our Session 3 practice. See if you are able to complete this exercise WITHOUT referencing any notes, documentation, etc.

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

paste all of your terminal text here

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

2. Git x Markdown Practice

See if you are able to complete this exercise WITHOUT referencing any notes, documentation, etc.

1. Create a directory called git_practice_2. Inside of there, create three files notes.md, README.md and mind_blown.jpg
2. Initialize the directory
3. Use git status to ensure you are set up for tracking using Git
4. Add all of the files to the staging area and check they have been added correctly
5. Create an initial commit (Note: Be sure to follow the correct message format for your first commit!)
6. Open your notes.md file in your text editor and add 1 heading, a bulleted list, and a code block.
7. Add the changes to the staging area
8. Commit the new changes
9. Check the status
10. Add an inline code snippet, bold text and a numbered list to your notes.md file
11. Add the changes to the staging area
12. Commit the new changes (Note: Be sure to follow convention for commit messages!)
13. Remove the README.md and mind_blown.jpg file from your git_practice_2 directory
14. Add the changes to the staging area
15. Commit the new changes
16. 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):

paste all of your terminal text here

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