CAREFULLY READ ALL THE INSTRUCTIONS BEFORE STARTING THESE EXERCISES!
To start this assignment:
- Click the button in the upper right-hand corner that says Fork. This is now your copy of the document.
- Click the Edit button when you're ready to start adding your answers.
- To save your work, click the green button in the bottom right-hand corner. You can always come back and re-edit your gist.
Read this article on git commit messages
- Your key take-aways OR how you're going to implement specific points (minimum 2):
- when writing commit subject lines, I'm going to think of them in terms of completing the sentence "If applied, this commit will - X" Honestly, this alone helps me understand exactly how to try and implement the subject line. Just finish the sentence.
- Key takeaway: being very specific and precise in commit language can be crucial to help save yourself many headaches, as well as the teams you may be working with.
- Key takeway: It seems like with most things coding related, consistent syntax is as crucial here with commit logs as it is with implementing code in quotations, using underscores or hyphens to separate words.
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:
- My impression the git staging area draws comparisons to a play that is performed on stage in a theater. I imagine the play/performance itself is the program, the actors and performers within are the files who have been programmed and brought together, and taught their individual role within the greater performance.
- Specifically, I view the git staging area as the dress rehearsal portion of the play/performance timeline. It is a space where the entire play/program has a chance to run its course, and the director has a chance to view individual elements of the greater whole, and make small changes in a safe space (the rehearsal / the staging area) before the play is fully committed/performed in front of a live audience.
- I hope that makes sense! I'm pulling my knowledge from my dramatic arts undergrad to try and connect the dots here with git commits. :)
Follow the steps below to practice the git workflow. Be ready to copy-paste your terminal output as confirmation of your practice.
- Create a directory called
git_homework. Inside of there, create a file calledthoughts.md - Initialize the directory
- Use
git statusto ensure you are set up for tracking using Git - Add your
thoughts.mdto the staging area - Check the
git status - Create an initial commit (Note: Be sure to follow the correct message format for your first commit!)
- Check the
git status - Add two takeaways you've had from your first few classes of Mod 0 as it relates to success at Turing.
- Check the
git status - Check the changes you've made using
git diff - Add the changes to the staging area
- Commit the new changes (Note: Be sure to follow convention for commit messages!)
- Check the status
- Add two new strategies you are committed to trying during the rest of Mod 0 to
thoughts.md - Add the changes to the staging area
- Commit the new changes (Note: Be sure to follow convention for commit messages!)
- Add at least one shoutout to someone who has helped you, supported you, or just been a positive presence in the last two weeks!
- Add the changes to the staging area
- Commit the new changes (Note: Be sure to follow convention for commit messages!)
- Show the log of your work in
onelineformat usinggit log(This will likely require some Googling)
Copy and paste all of the terminal text from this process below (not just the history):
/Users/colgan $mkdir git_homework
/Users/colgan $ls
Applications Movies git_homework
Desktop Music session3_practice
Documents Pictures to_do
Downloads Public turing
Library cool_project
/Users/colgan $cd git_homework
/Users/colgan/git_homework $git init
Initialized empty Git repository in /Users/colgan/git_homework/.git/
/Users/colgan/git_homework main $git status
On branch main
No commits yet
nothing to commit (create/copy files and use "git add" to track)
/Users/colgan/git_homework main $touch thoughts.md
/Users/colgan/git_homework main $git status
On branch main
No commits yet
Untracked files:
(use "git add <file>..." to include in what will be committed)
thoughts.md
nothing added to commit but untracked files present (use "git add" to track)
/Users/colgan/git_homework main $git commit -m "add thoughts"
On branch main
Initial commit
Untracked files:
(use "git add <file>..." to include in what will be committed)
thoughts.md
nothing added to commit but untracked files present (use "git add" to track)
/Users/colgan/git_homework main $git add thoughts.md
/Users/colgan/git_homework main $git commit -m "add thoughts.md"
[main (root-commit) 913ffdd] add thoughts.md
1 file changed, 0 insertions(+), 0 deletions(-)
create mode 100644 thoughts.md
/Users/colgan/git_homework main $git status
On branch main
nothing to commit, working tree clean
/Users/colgan/git_homework main $atom thoughts.md
/Users/colgan/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/colgan/git_homework main $git diff
diff --git a/thoughts.md b/thoughts.md
index e69de29..b3c5a67 100644
--- a/thoughts.md
+++ b/thoughts.md
@@ -0,0 +1,3 @@
+Takeaways from initial Mod 0 Sessions as it relates to success at Turing:
+* well thought out notes, supplemented with charts, diagrams, and color coding can be an invaluable resource for your overall success
+* taking time to do work outside of coding environments is crucial. actions such as psuedo-coding can really help you get your mindset into the problem you're trying to solve. It also helps you make sure you actually understand the task at hand.
/Users/colgan/git_homework main $git add thoughts.md
/Users/colgan/git_homework main $git diff
/Users/colgan/git_homework main $git commit -m "update thoughts.md"
[main a8e8982] update thoughts.md
1 file changed, 3 insertions(+)
/Users/colgan/git_homework main $git status
On branch main
nothing to commit, working tree clean
/Users/colgan/git_homework main $atom thoughts.md
/Users/colgan/git_homework main $git diff
diff --git a/thoughts.md b/thoughts.md
index b3c5a67..cd0d300 100644
--- a/thoughts.md
+++ b/thoughts.md
@@ -1,3 +1,7 @@
Takeaways from initial Mod 0 Sessions as it relates to success at Turing:
* well thought out notes, supplemented with charts, diagrams, and color coding can be an invaluable resource for your overall success
-* taking time to do work outside of coding environments is crucial. actions such as psuedo-coding can really help you get your mindset into the problem you're trying to solve. It also helps you make sure you actually understand the task at hand.
+* taking time to do work outside of coding environments is crucial. actions such as psuedo-coding can really help you get your mindset into the problem you're trying to solve. It also helps you make sure you actually understand the task at hand.
+
+During Mod 0 - I'm committing to:
+* take better notes than I ever knew I could take when I was in highschool and undergrad
+* pratice coding to some degree every single day, to try and utilize the info being taught during the Mod 0 sessions.
/Users/colgan/git_homework main $git add thoughts.md
/Users/colgan/git_homework main $git commit -m "think about Mod 0 strategies"
[main bfbdda8] think about Mod 0 strategies
1 file changed, 5 insertions(+), 1 deletion(-)
/Users/colgan/git_homework main $atom thoughts.md
/Users/colgan/git_homework main $
/Users/colgan/git_homework main $git diff
diff --git a/thoughts.md b/thoughts.md
index cd0d300..a5c6650 100644
--- a/thoughts.md
+++ b/thoughts.md
@@ -4,4 +4,7 @@ Takeaways from initial Mod 0 Sessions as it relates to success at Turing:
During Mod 0 - I'm committing to:
* take better notes than I ever knew I could take when I was in highschool and undergrad
-* pratice coding to some degree every single day, to try and utilize the info being taught during the Mod 0 sessions.
+* pratice coding to some degree every single day, to try and utilize the info being taught during the Mod 0 sessions.
+
+
+Shoutout to Vanessa Randall - an awesome friend who encouraged me to try coding, encouraged me to apply to Turing, and has been an awesome friend and supporter since I've met her. She's an awesome lady, and if you are fortunate enough to know her, you are better off for it.
/Users/colgan/git_homework main $git add thoughts.md
/Users/colgan/git_homework main $git commit -m "shout out your friends"
[main 15be8a9] shout out your friends
1 file changed, 4 insertions(+), 1 deletion(-)
/Users/colgan/git_homework main $git log
commit 15be8a90723ef03d8de8c19515f4b1f85cb12303 (HEAD -> main)
Author: Colgan Meanor <colganmeanor7@gmail.com>
Date: Wed Jul 21 22:02:38 2021 -0500
shout out your friends
commit bfbdda8d69986b98a41215d8a6cc95bd757b7c71
Author: Colgan Meanor <colganmeanor7@gmail.com>
Date: Wed Jul 21 21:59:49 2021 -0500
think about Mod 0 strategies
commit a8e89826c366cc0daf74b1f8b37ca5cc763c2c8a
Author: Colgan Meanor <colganmeanor7@gmail.com>
Date: Wed Jul 21 21:55:16 2021 -0500
update thoughts.md
commit 913ffdd30dd063853e9c163c1f1b9e82b96cd04d
Author: Colgan Meanor <colganmeanor7@gmail.com>
Date: Wed Jul 21 21:44:53 2021 -0500
add thoughts.md
/Users/colgan/git_homework main $git log --pretty=oneline
15be8a90723ef03d8de8c19515f4b1f85cb12303 (HEAD -> main) shout out your friends
bfbdda8d69986b98a41215d8a6cc95bd757b7c71 think about Mod 0 strategies
a8e89826c366cc0daf74b1f8b37ca5cc763c2c8a update thoughts.md
913ffdd30dd063853e9c163c1f1b9e82b96cd04d add thoughts.md
/Users/colgan/git_homework main $
IMPORTANT: Do NOT remove this git_homework directory. You will be using this directory during the next session.
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
- ⚡️ TURN THIS SENTENCE INTO A LINK TO YOUR GIST ⚡️
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
If you have any questions, comments, or confusions that you would like an instructor to address, list them below:
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 formattingfor single lines of code/error messages - If I provided larger blocks of code, I used a code snippet in the correct format (such as
.jsor.rb)
- If I provided short code examples, I used
- 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
I love the way you approach the commit message, makes sense to me! Also, your staging analogy is great! Good work on all the prompts! (btw you're gonna be making that Kanye face a lot at Turing haha)