Skip to content

Instantly share code, notes, and snippets.

Show Gist options
  • Save brycemara/1950cab5b84091e581e69f13e49e67d1 to your computer and use it in GitHub Desktop.
Save brycemara/1950cab5b84091e581e69f13e49e67d1 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:

408m kdir session_3_practice
409 cd session_3_practice
410  touch budget.csv mentors.txt
411  ls
412  mkdir notes
413  cd notes
414  touch git_notes.txt command_line_notes.txt
415  ls
416  cd ..
417  mkdir practice
418  cd practice
419  touch git_practice.txt
420  mkdir projects
421  cd projects
422  touch game.js
423  ls
424  cd ../..
425  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 (yes, oneline, not a spelling error) format

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

/Users/brycemarajarrett $mkdir git_hw

/Users/brycemarajarrett $cd git_hw

/Users/brycemarajarrett/git_hw $touch lines.txt

/Users/brycemarajarrett/git_hw $ls lines.txt

/Users/brycemarajarrett/git_hw $git init Initialized empty Git repository in /Users/brycemarajarrett/git_hw/.git/

/Users/brycemarajarrett/git_hw master $git status On branch master

No commits yet

Untracked files: (use "git add ..." to include in what will be committed) lines.txt

nothing added to commit but untracked files present (use "git add" to track)

/Users/brycemarajarrett/git_hw master $git add lines.txt

/Users/brycemarajarrett/git_hw master $git status On branch master

No commits yet

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

/Users/brycemarajarrett/git_hw master $git commit -m "Initial Commit" [master (root-commit) 2b84ee2] Initial Commit 1 file changed, 0 insertions(+), 0 deletions(-) create mode 100644 lines.txt

/Users/brycemarajarrett/git_hw master $git status On branch master nothing to commit, working tree clean

/Users/brycemarajarrett/git_hw master $git diff

/Users/brycemarajarrett/git_hw master $atom lines.txt

/Users/brycemarajarrett/git_hw master $git diff diff --git a/lines.txt b/lines.txt index e69de29..bed0157 100644 --- a/lines.txt +++ b/lines.txt @@ -0,0 +1,3 @@ +New changes here. + +"That's life"

/Users/brycemarajarrett/git_hw master $git add lines.txt

/Users/brycemarajarrett/git_hw master $git commit -m "Second Commit" [master dfe819d] Second Commit 1 file changed, 3 insertions(+)

/Users/brycemarajarrett/git_hw master $git status On branch master nothing to commit, working tree clean 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)
  • color (string)
  • length (integer)

Methods:

  • break_down
  • stack
  • crush
  • 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 like an instructor to address, list them below:

  1. The git portion was still pretty confusing to me. Specifically when asked to diff?

Extensions

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

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

@brycemara
Copy link
Author

brycemara commented Jul 24, 2020

@mschae16
Yes I'll redo it! How should I go about that since git_homework and quotes.txt have already been created? Should I just use different names? Thanks!

@mschae16
Copy link

@brycemara - Yep, totally fine to use different names for the second pass.

@brycemara
Copy link
Author

brycemara commented Jul 24, 2020

@mschae16 I've redone the task and added my new work to the gist. I accidentally skipped a step so that's why I used git diff twice, first time I hadn't made changes (because I'd skipped that step) so then I had to go in make changes then do git diff. I re-watched the lecture discussing the git diagram and I think I have much better understanding now.

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