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:
72 cd 73 mkdir session_3_practice 74 ls 75 cd session_3_practice 76 touch budget.csv 77 touch mentors.txt 78 mkdir notes 79 cd notes 80 touch git_notes.txt 81 touch command_line_notes.txt 82 cd .. 83 mkdir practice 84 cd practice 85 touch git_practice.txt 86 mkdir projects 87 cd projects 88 touch game.js 89 cd 90 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.
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):
edwindelbosque~$ mkdir git_homework edwindelbosque~$ cd git_homework edwindelbosque~/git_homework$ touch quotes.txt edwindelbosque~/git_homework$ git init Initialized empty Git repository in /Users/edwindelbosque/git_homework/.git/ edwindelbosque~/git_homework$ git status On branch master
No commits yet
Untracked files: (use "git add ..." to include in what will be committed)
quotes.txt
nothing added to commit but untracked files present (use "git add" to track) edwindelbosque~/git_homework$ git add quotes.txt edwindelbosque~/git_homework$ git status On branch master
No commits yet
Changes to be committed: (use "git rm --cached ..." to unstage)
new file: quotes.txt
edwindelbosque~/git_homework$ git commit -m "Initial commit" [master (root-commit) c1ae6a5] Initial commit Committer: Alan Turing [email protected] Your name and email address were configured automatically based on your username and hostname. Please check that they are accurate. You can suppress this message by setting them explicitly:
git config --global user.name "Your Name"
git config --global user.email [email protected]
After doing this, you may fix the identity used for this commit with:
git commit --amend --reset-author
1 file changed, 0 insertions(+), 0 deletions(-) create mode 100644 quotes.txt edwindelbosque~/git_homework[master]$ git status On branch master nothing to commit, working tree clean edwindelbosque~/git_homework[master]$ echo "Luck is what happens when preparation meets opportunity" >> quotes.txt edwindelbosque~/git_homework[master !]$ git status On branch master Changes not staged for commit: (use "git add ..." to update what will be committed) (use "git checkout -- ..." to discard changes in working directory)
modified: quotes.txt
no changes added to commit (use "git add" and/or "git commit -a") edwindelbosque~/git_homework[master !]$ git diff quotes.txt diff --git a/quotes.txt b/quotes.txt index e69de29..9ab2e4c 100644 --- a/quotes.txt +++ b/quotes.txt @@ -0,0 +1 @@ +Luck is what happens when preparation meets opportunity edwindelbosque~/git_homework[master !]$ git add Nothing specified, nothing added. Maybe you wanted to say 'git add .'? edwindelbosque~/git_homework[master !]$ git add quotes.txt edwindelbosque~/git_homework[master !]$ git status On branch master Changes to be committed: (use "git reset HEAD ..." to unstage)
modified: quotes.txt
edwindelbosque~/git_homework[master !]$ git commit -m "Add favorite quote" [master 0d8eafe] Add favorite quote Committer: Alan Turing [email protected] Your name and email address were configured automatically based on your username and hostname. Please check that they are accurate. You can suppress this message by setting them explicitly:
git config --global user.name "Your Name"
git config --global user.email [email protected]
After doing this, you may fix the identity used for this commit with:
git commit --amend --reset-author
1 file changed, 1 insertion(+) edwindelbosque~/git_homework[master]$ git status On branch master nothing to commit, working tree clean edwindelbosque~/git_homework[master]$
IMPORTANT: Do not remove this git_homework directory. You will be using this directory during Thursday's session.
If you have any questions, comments, or confusions that you would an instructor to address, list them below:
- No questions!
-
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.

Nice work, @edwindelbosque! Next time try formatting your copy-pasted code by adding three backtics (key left of the letter one)
```before and after your code block. This will come in handy when you are trying to Slack people code snippets as well.