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.
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:
jamesweist~$ mkdir session_3_practice
jamesweist~$ ls
Applications Google Drive Pictures
Desktop Library Public
Documents Movies session_3_practice
Downloads Music
jamesweist~$ cd
jamesweist~$ cd session_3_practice
jamesweist~/session_3_practice$ touch budget.csv
jamesweist~/session_3_practice$ touch mentors.txt
jamesweist~/session_3_practice$ mkdir notes
jamesweist~/session_3_practice$ cd notes
jamesweist~/session_3_practice/notes$ touch git_notes.txt
jamesweist~/session_3_practice/notes$ touch command_line_notes.txt
jamesweist~/session_3_practice/notes$ cd ..
jamesweist~/session_3_practice$ ls
budget.csv mentors.txt notes
jamesweist~/session_3_practice$ mkdir practice
jamesweist~/session_3_practice$ cd practice
jamesweist~/session_3_practice/practice$ touch git_practice.txt
jamesweist~/session_3_practice/practice$ mkdir projects
jamesweist~/session_3_practice/practice$ cd projects
jamesweist~/session_3_practice/practice/projects$ touch game.js
jamesweist~/session_3_practice/practice/projects$ ls
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.txt
file to the staging area - Check the git status
- Create an initial commit
- Check the status
- Add your favorite quote to the
quotes.txt
file - 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):
jamesweist~$ mkdir git_homework
jamesweist~$ cd git_homework
jamesweist~/git_homework$ touch quotes.txt
jamesweist~/git_homework$ git init
Initialized empty Git repository in /Users/jamesweist/git_homework/.git/
jamesweist~/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)
jamesweist~/git_homework$ git commit -m "Initial commit"
On branch master
Initial commit
Untracked files:
quotes.txt
nothing added to commit but untracked files present
jamesweist~/git_homework$ add quotes.txt
-bash: add: command not found
jamesweist~/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)
jamesweist~/git_homework$ git add quotes.txt
jamesweist~/git_homework$ git commit -m "Initial commit"
[master (root-commit) 3a850af] Initial commit
1 file changed, 0 insertions(+), 0 deletions(-)
create mode 100644 quotes.txt
jamesweist~/git_homework[master]$ echo "You really are a funny guy"
You really are a funny guy
jamesweist~/git_homework[master]$ git status
On branch master
nothing to commit, working tree clean
jamesweist~/git_homework[master]$ echo "You really are a funny guy" >> quotes.txt
jamesweist~/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")
jamesweist~/git_homework[master !]$ git diff
diff --git a/quotes.txt b/quotes.txt
index e69de29..36d84cd 100644
--- a/quotes.txt
+++ b/quotes.txt
@@ -0,0 +1 @@
+You really are a funny guy
jamesweist~/git_homework[master !]$ git commit -m "Quotes added"
On branch master
Changes not staged for commit:
modified: quotes.txt
no changes added to commit
jamesweist~/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")
jamesweist~/git_homework[master !]$ git diff quotes.txt
diff --git a/quotes.txt b/quotes.txt
index e69de29..36d84cd 100644
--- a/quotes.txt
+++ b/quotes.txt
@@ -0,0 +1 @@
+You really are a funny guy
jamesweist~/git_homework[master !]$ git add quotes.txt
jamesweist~/git_homework[master !]$ git commit -m "Quotes added"
[master 1c99773] Quotes added
1 file changed, 1 insertion(+)
jamesweist~/git_homework[master]$ git status
On branch master
nothing to commit, working tree clean
jamesweist~/git_homework[master]$
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)
- shape (______)
- Thickness (integer)
Methods:
- break_down
- stack
- open
- closed
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.
added terminal commands for file structure