Mod 0 Session 3 Practice Tasks - Samantha Freeman

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:

   38  mkdir session_3_practice
   39  cd session_3_practice
   40  touch budget.csv
   41  touch mentors.txt
   42  mkdir notes
   43  mkdir practice
   44  ls
   45  cd notes
   46  touch git_notes.txt
   47  touch command_line_notes.txt
   48  ls
   49  cd ..
   50  cd practice
   51  touch git_practice.txt
   52  mkdir projects
   53  ls
   54  cd projects
   55  touch game.js
   56  ls

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

samanthafreeman~$ pwd
/Users/samanthafreeman
samanthafreeman~$ mkdir git_homework
samanthafreeman~$ ls
Applications	Documents	Library		Music		Public
Desktop		Downloads	Movies		Pictures	git_homework
samanthafreeman~$ cd git_homework
samanthafreeman~/git_homework$ touch quotes.txt
samanthafreeman~/git_homework$ ls
quotes.txt
samanthafreeman~/git_homework$ git init
Initialized empty Git repository in /Users/samanthafreeman/git_homework/.git/
samanthafreeman~/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)
samanthafreeman~/git_homework$ git add quotes.txt
samanthafreeman~/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

samanthafreeman~/git_homework$ git commit -m 'initial commit'
[master (root-commit) 059b5f2] initial commit
 1 file changed, 0 insertions(+), 0 deletions(-)
 create mode 100644 quotes.txt
samanthafreeman~/git_homework[master]$ git status
On branch master
nothing to commit, working tree clean
samanthafreeman~/git_homework[master]$ echo "What we've got here is a failure to communicate" >> quotes.txt
samanthafreeman~/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")
samanthafreeman~/git_homework[master !]$ git diff
diff --git a/quotes.txt b/quotes.txt
index e69de29..6df665d 100644
--- a/quotes.txt
+++ b/quotes.txt
@@ -0,0 +1 @@
+What we've got here is a failure to communicate
samanthafreeman~/git_homework[master !]$ git add quotes.txt
samanthafreeman~/git_homework[master !]$ git commit -m 'Added first quote'
[master 2fc8730] Added first quote
 1 file changed, 1 insertion(+)
samanthafreeman~/git_homework[master]$ git status
On branch master
nothing to commit, working tree clean
samanthafreeman~/git_homework[master]$ samanthafreeman~$ pwd
-bash: samanthafreeman~$: command not found
samanthafreeman~/git_homework[master]$ /Users/samanthafreeman
-bash: /Users/samanthafreeman: is a directory

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. What exactly does the phrase "working tree clean" mean?

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, @SamanthaLFreeman! Good question about "working tree clean". Working tree refers to the current directory where you are doing your work. You get the message "working tree clean" when there are no changes to add to the staging area. Your working tree is clean because everything has moved to the staging area.