Skip to content

Instantly share code, notes, and snippets.

Show Gist options
  • Select an option

  • Save tylorschafer/97a24f17a03e63918dde04c2b186e644 to your computer and use it in GitHub Desktop.

Select an option

Save tylorschafer/97a24f17a03e63918dde04c2b186e644 to your computer and use it in GitHub Desktop.
Mod 0 Session 3 Practice Tasks

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:

   27  cd t_schafer
   28  mkdir session_3_practice
   29  ls
   30  cd session_3_practice
   31  touch budget.csv
   32  ls
   33  touch mentors.txt
   34  ls
   35  cd ..
   36  ls
   37  cd sessions_3_practice
   38  cd session_3_practice
   39  mkdir notes
   40  cd notes
   41  touch git_notes.txt
   42  touch git_command_line_notes.txt
   43  ls
   44  cd ..
   45  ls
   46  mkdir practice
   47  cd practice
   48  touch git_practice.txt
   49  ls
   50  mkdir projects
   51  cd projects
   52  touch game.js
   53  history

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

t_schafer~$ mkdir git_homework
t_schafer~$ cd git_homework
t_schafer~/git_homework$ touch quotes.txt
t_schafer~/git_homework$ git init
Initialized empty Git repository in /Users/t_schafer/git_homework/.git/
t_schafer~/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)
t_schafer~/git_homework$ git add quotes.txt
t_schafer~/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

t_schafer~/git_homework$ git commit -m 'Inital commit'
[master (root-commit) 904a67b] Inital commit
 1 file changed, 0 insertions(+), 0 deletions(-)
 create mode 100644 quotes.txt
t_schafer~/git_homework[master]$ git status
On branch master
nothing to commit, working tree clean
t_schafer~/git_homework[master]$ echo "never memorize something you can look up." >> quotes.txt
t_schafer~/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")
t_schafer~/git_homework[master !]$ git diff
diff --git a/quotes.txt b/quotes.txt
index e69de29..e88e38c 100644
--- a/quotes.txt
+++ b/quotes.txt
@@ -0,0 +1 @@
+never memorize something you can look up.
t_schafer~/git_homework[master !]$ git add
Nothing specified, nothing added.
Maybe you wanted to say 'git add .'?
t_schafer~/git_homework[master !]$ git add quotes.txt
t_schafer~/git_homework[master !]$ git commit -m 'Final commit'
[master 3068d87] Final commit
 1 file changed, 1 insertion(+)
t_schafer~/git_homework[master]$ git status
On branch master
nothing to commit, working tree clean
t_schafer~/git_homework[master]$ git log --pretty=oneline
3068d875b7263ed350e96737ffb79883746cde22 (HEAD -> master) Final commit
904a67b4419a756d07fc2c04d7ec99723a1443e1 Inital commit

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. This git excercise really cemented some git concepts for me. Helped a ton! I am curious if that was the correct way to log in 'oneline' format. Other than that everything else was very straightforward.

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.

@katiescruggs
Copy link

Awesome job, @tylorschafer! Everything looks correct, and I'm glad that git is making sense for you! As far as the correct way to git log oneline, I usually do git log --oneline because it's shorter to type. Apparently it's shorthand for --pretty=oneline --abbrev-commit: https://git-scm.com/book/en/v2/Git-Basics-Viewing-the-Commit-History. But --pretty=oneline is perfectly good too! More than one way to achieve a goal sometimes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment