Skip to content

Instantly share code, notes, and snippets.

Show Gist options
  • Save GreysonElkins/f749a1934f5e5aecd898db365d0f7711 to your computer and use it in GitHub Desktop.
Save GreysonElkins/f749a1934f5e5aecd898db365d0f7711 to your computer and use it in GitHub Desktop.
Mod 0 Session 2 Practice Tasks

Session 2 Practice Tasks

The assignments listed here should take you approximately 55 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:

  183  mkdir session_3_practice
  184  cd session_3_practice
  185  touch budget.csv mentors.txt
  186  mkdir notes practice
  187  ls
  188  cd notes
  189  touch git_notes.txt command_line_notes.txt
  190  cd ../practice
  191  touch git_practice.txt
  192  mkdir projects
  193  cd projects
  194  touch game.js 

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 (yes, oneline, not a spelling error) format

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

/Users/grey  $mkdir git_homework
/Users/grey  $cd git_homework
/Users/grey/git_homework  $touch quotes.txt
/Users/grey/git_homework  $git init
Initialized empty Git repository in /Users/grey/git_homework/.git/
/Users/grey/git_homework master $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)
/Users/grey/git_homework master $git add quotes.txt
/Users/grey/git_homework master $git status
On branch master

No commits yet

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

/Users/grey/git_homework master $git commit -m "initial commit"
[master (root-commit) 8a5188a] initial commit
 1 file changed, 0 insertions(+), 0 deletions(-)
 create mode 100644 quotes.txt
/Users/grey/git_homework master $git status
On branch master
nothing to commit, working tree clean
/Users/grey/git_homework master $atom .
/Users/grey/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 restore <file>..." to discard changes in working directory)
	modified:   quotes.txt

no changes added to commit (use "git add" and/or "git commit -a")
/Users/grey/git_homework master $git diff
diff --git a/quotes.txt b/quotes.txt
index e69de29..6979394 100644
--- a/quotes.txt
+++ b/quotes.txt
@@ -0,0 +1 @@
+"Some people confuse inspiration with lightning not me I know it comes... at my command like a turkey club sandwich with a cup of split pea soup or tones from Benny Goodman's clarinet..." - David Lehman
/Users/grey/git_homework master $git add quotes.txt
/Users/grey/git_homework master $git commit -m "new changes"
[master f68a0d1] new changes
 1 file changed, 1 insertion(+)
/Users/grey/git_homework master $git status
On branch master
nothing to commit, working tree clean
/Users/grey/git_homework master $git log --oneline
f68a0d1 (HEAD -> master) new changes
8a5188a initial commit
/Users/grey/git_homework master $history
  302  mkdir git_homework
  303  cd git_homework
  304  touch quotes.txt
  305  git init
  306  git status
  307  git add quotes.txt
  308  git status
  309  git commit -m "initial commit"
  310  git status
  311  atom .
  312  git status
  313  git diff
  314  git add quotes.txt
  315  git commit -m "new changes"
  316  git status
  317  git log --oneline
/Users/grey/git_homework master $

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

3. Classes, Attributes, and Methods (15 min)

Look at the template below for a CardboardBox class. Fill in missing blanks with additional attributes and methods.

Class: CardboardBox

Attributes:

  • width (integer)
  • depth (integer)
  • wet (boolean)
  • height (integer)

Methods:

  • break_down
  • stack
  • pack
  • tear

4. Modify your Zsh Prompt (10 min)

  • Make sure that your shell is set to zsh by running the following command: $ chsh -s /bin/zsh. Remember to omit the $! Note that macOS Catalina and later operating systems already use zsh as the default shell.

  • Watch this video and follow each step to modify your own zshrc configuration file. As mentioned in the video, you will need this snippet below:

# Load version control information
autoload -Uz vcs_info
precmd() { vcs_info }

# Format the vcs_info_msg_0_ variable
zstyle ':vcs_info:git:*' formats '%b'

# Determine if current working directory is a git repository
git_branch_color() {
  if current_git_status=$(git status 2> /dev/null); then
    parse_git_dirty
  else
    echo ""
  fi
}

# Change branch color if working tree is clean
parse_git_dirty() {
  if current_git_status=$(git status | grep 'Changes to be committed:\|Untracked files:\|modified:|deleted:' 2> /dev/null); then
    echo "%F{red}"
  else
    echo "%F{green}"
  fi
}

# Set up the prompt (with git branch name)
setopt PROMPT_SUBST
PROMPT='%F{white}%d $(git_branch_color)${vcs_info_msg_0_} %f$'

5. Questions/Comments/Confusions

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

  1. Just want to make sure that I didn't need to include anything about changing to zsh (I already did this a few days ago)

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.

@francepack
Copy link

@GreysonElkins
Looks good to me! Nice foresight adding multiple files/directories on one line. Also, good job with casing in your class. Reach out if you have questions come up about navigating the terminal. I'd highly recommend checking out extension #4 if you are unfamiliar with tab complete- getting used to doing that early on makes life much easier!

And you're all set- Part 4 doesn't need any update.

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