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.
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:
35 cd
36 mkdir session_3_practice
37 cd session_3_practice
38 touch budget.csv
39 touch mentors.txt
40 mkdir notes
41 cd notes
42 touch git_notes.txt
43 touch command_line_notes.txt
44 cd..
45 cd ..
46 mkdir practice
47 cd practice
48 touch git_practice.txt
49 mkdir projects
50 cd projects
51 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.
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.
- Create a directory called
git_homework. Inside of there, create a file calledquotes.txt. - Initialize the directory
- Check the git status
- Add your
quotes.txtfile to the staging area - Check the git status
- Create an initial commit
- Check the status
- Add your favorite quote to the
quotes.txtfile - Check the status
- Check the diff
- Add the changes to the staging area
- Commit the new changes
- Check the status
- 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):
Last login: Fri Sep 6 07:45:49 on ttys001
Carlas-MacBook-Pro:~ carla$ cd
Carlas-MacBook-Pro:~ carla$ mkdir git_homework
Carlas-MacBook-Pro:~ carla$ cd git_homework
Carlas-MacBook-Pro:git_homework carla$ touch quotes.txt
Carlas-MacBook-Pro:git_homework carla$ git init
Initialized empty Git repository in /Users/carla/git_homework/.git/
Carlas-MacBook-Pro:git_homework carla$ 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)
Carlas-MacBook-Pro:git_homework carla$ git add quotes.txt
Carlas-MacBook-Pro:git_homework carla$ git commit -m 'initial commit'
[master (root-commit) 58542a5] initial commit
1 file changed, 0 insertions(+), 0 deletions(-)
create mode 100644 quotes.txt
Carlas-MacBook-Pro:git_homework carla$ git status
On branch master
nothing to commit, working tree clean
Carlas-MacBook-Pro:git_homework carla$ atom .
Carlas-MacBook-Pro:git_homework carla$ 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")
Carlas-MacBook-Pro:git_homework carla$ git diff quotes.txt
diff --git a/quotes.txt b/quotes.txt
index e69de29..2c24cf5 100644
--- a/quotes.txt
+++ b/quotes.txt
@@ -0,0 +1 @@
+Stay golden, ponyboy
Carlas-MacBook-Pro:git_homework carla$ git add quotes.txt
Carlas-MacBook-Pro:git_homework carla$ git commit -m 'Quote added'
[master b469b1b] Quote added
1 file changed, 1 insertion(+)
Carlas-MacBook-Pro:git_homework carla$ git status
On branch master
nothing to commit, working tree clean
Carlas-MacBook-Pro:git_homework carla$ git log --oneline
b469b1b (HEAD -> master) Quote added
58542a5 initial commit
Carlas-MacBook-Pro:git_homework carla$
IMPORTANT: Do not remove this git_homework directory. You will be using this directory during Thursday's session.
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)
- weight (float)
- length (integer)
Methods:
- break_down
- stack
- fill
- empty
- Watch this video and follow each step to modify your own bash profile. As mentioned in the video, you will need this snippet below:
# get current branch in git repo
function parse_git_branch() {
BRANCH=`git branch 2> /dev/null | sed -e '/^[^*]/d' -e 's/* \(.*\)/\1/'`
if [ ! "${BRANCH}" == "" ]
then
STAT=`parse_git_dirty`
echo "[${BRANCH}${STAT}]"
else
echo ""
fi
}
# get current status of git repo
function parse_git_dirty {
status=`git status 2>&1 | tee`
dirty=`echo -n "${status}" 2> /dev/null | grep "modified:" &> /dev/null; echo "$?"`
untracked=`echo -n "${status}" 2> /dev/null | grep "Untracked files" &> /dev/null; echo "$?"`
ahead=`echo -n "${status}" 2> /dev/null | grep "Your branch is ahead of" &> /dev/null; echo "$?"`
newfile=`echo -n "${status}" 2> /dev/null | grep "new file:" &> /dev/null; echo "$?"`
renamed=`echo -n "${status}" 2> /dev/null | grep "renamed:" &> /dev/null; echo "$?"`
deleted=`echo -n "${status}" 2> /dev/null | grep "deleted:" &> /dev/null; echo "$?"`
bits=''
if [ "${renamed}" == "0" ]; then
bits=">${bits}"
fi
if [ "${ahead}" == "0" ]; then
bits="*${bits}"
fi
if [ "${newfile}" == "0" ]; then
bits="+${bits}"
fi
if [ "${untracked}" == "0" ]; then
bits="?${bits}"
fi
if [ "${deleted}" == "0" ]; then
bits="x${bits}"
fi
if [ "${dirty}" == "0" ]; then
bits="!${bits}"
fi
if [ ! "${bits}" == "" ]; then
echo " ${bits}"
else
echo ""
fi
}
export PS1="\u\w\`parse_git_branch\`$ "
If you have any questions, comments, or confusions that you would an instructor to address, list them below:
-
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.
-
This course is how I personally learned command line. If time permits, I highly recommend reading and practicing.
-
Also recommended by Jeff Casimir: Michael Hartl's Learn Enough Command Line.
-
Add tab completion to make your life easier: Type Less. Do More.
