Mod 0 Session 3 Practice Tasks

mod_0_session_3_practice_tasks.md

Session 3 Practice Tasks

The assignments listed here should take you approximately 25 total minutes.

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.

1. Creating Files and Directories (10 min)

Need help? You can go back to the files/directories portion of the lesson here.

Scroll down to the bottom of this page and look at the image of the directories and files. Use commands in your terminal to create the directories and files structured exactly how they appear in the image.

When you're done, type history to see your commands. Copy and paste the commands that were used to create the directory and files:

  245  mkdir session_3_practice
  246  ls
  247  cd session_3_practice
  248  touch budget.csv
  249  touch mentor.txt
  250  mkdir notes
  251  ls
  252  cd notes
  253  touch git_notes.txt
  254  command_line_notes.txt
  255  touch command_line_notes.txt
  256  cd ..
  257  mkdir practice
  258  ls
  259  cd practice
  260  touch git_practice.txt
  261  cd ..
  262  mkdir projects
  263  cd projects
  264  ls
  265  cd ..
  266  ls
  267  cd projects
  268  cd ..
  269  cd projects
  270  cd ..
  271  cds practice
  272  cd practice
  273  cd projects
  274  touch projects
  275  cd projects
  276  ls
  277  /projetcs mkdir game.js
  278  cd ..
  279  cd projects
  280  touch game.js
  281  ls
  282  cd../../

There was one or two parts that took an extra move but getting better.

Since this is just a practice directory, feel free to remove the parent directory session_3_practice when you're done with this exercise.

2. Git Practice (15 min)

You can reference the files/directories portion of the lesson here.

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 quotes.txt.
2. Initialize the directory
3. Check the git status
4. Add your quotes.txt file to the staging area
5. Check the git status
6. Create an initial commit
7. Check the status
8. Add your favorite quote to the quotes.txt file
9. Check the status
10. Check the diff
11. Add the changes to the staging area
12. Commit the new changes
13. Check the status
14. Show the log in oneline format

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

garrettiannuzzi~$ mkdir git_homework
garrettiannuzzi~$ cd git_homework
garrettiannuzzi~/git_homework$ touch quotes.txt
garrettiannuzzi~/git_homework$ git init
Initialized empty Git repository in /Users/garrettiannuzzi/git_homework/.git/
garrettiannuzzi~/git_homework$ git status
On branch master

No commits yet

Untracked files:
  (use "git add <file>..." to include in what will be committed)

	quotes.txt

nothing added to commit but untracked files present (use "git add" to track)
garrettiannuzzi~/git_homework$ git add quotes.txt
garrettiannuzzi~/git_homework$ git status
On branch master

No commits yet

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

	new file:   quotes.txt

garrettiannuzzi~/git_homework$ git commit -m "initial commit"
[master (root-commit) f9fb645] initial commit
 1 file changed, 0 insertions(+), 0 deletions(-)
 create mode 100644 quotes.txt
garrettiannuzzi~/git_homework[master]$ git status
On branch master
nothing to commit, working tree clean
garrettiannuzzi~/git_homework[master]$ echo "Follow your heart but take your brain with you" >>quotes.txt
garrettiannuzzi~/git_homework[master !]$ git status
On branch master
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

	modified:   quotes.txt

no changes added to commit (use "git add" and/or "git commit -a")
garrettiannuzzi~/git_homework[master !]$ git diff quotes.txt
diff --git a/quotes.txt b/quotes.txt
index e69de29..cd84b23 100644
--- a/quotes.txt
+++ b/quotes.txt
@@ -0,0 +1 @@
+Follow your heart but take your brain with you
garrettiannuzzi~/git_homework[master !]$ git add quotes.txt
garrettiannuzzi~/git_homework[master !]$ git status
On branch master
Changes to be committed:
  (use "git reset HEAD <file>..." to unstage)

	modified:   quotes.txt

garrettiannuzzi~/git_homework[master !]$ git log --oneline
f9fb645 (HEAD -> master) initial commit
garrettiannuzzi~/git_homework[master !]$ 

IMPORTANT: Do not remove this git_homework directory. You will be using this directory during Thursday's session.

3. Questions/Comments/Confusions

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

1. I am getting through about 90% of the git stuff without a problem but there always seems to be one little thing that messes it up. It's also kind of hard to read through it all and understand the error messages but just need more practice.

Extensions

1. If time permits and you want extra git practice and alternative explanations (it's often beneficial to have something explained in many different ways), check out Codecademy's Git Course, particularly the first free item on the syllabus, "Basic Git Workflow". In Mod 0, we will not cover anything beyond Codecademy's intro section; however, you are welcome to check out the other git lessons listed on the syllabus if you want a head start.

2. This course is how I personally learned command line. If time permits, I highly recommend reading and practicing.

3. Also recommended by Jeff Casimir: Michael Hartl's Learn Enough Command Line.

4. Add tab completion to make your life easier: Type Less. Do More.

z_img_1.png

Great job, @Garrett-Iannuzzi! You are right that it can be confusing to read git error messages at first, but your terminal output from the git section looks good. It looks like you just forgot to commit your second part of changes (step 12).