0% found this document useful (0 votes)
171 views5 pages

Notes On Git

Git allows tracking changes to projects over time. It records changes, stores them, and allows referencing past versions. The document then demonstrates initializing a Git project called "sorcerers-code", adding and editing files, checking statuses and differences between versions, staging changes, and making an initial commit with a short message.
Copyright
© © All Rights Reserved
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
Download as txt, pdf, or txt
0% found this document useful (0 votes)
171 views5 pages

Notes On Git

Git allows tracking changes to projects over time. It records changes, stores them, and allows referencing past versions. The document then demonstrates initializing a Git project called "sorcerers-code", adding and editing files, checking statuses and differences between versions, staging changes, and making an initial commit with a short message.
Copyright
© © All Rights Reserved
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
Download as txt, pdf, or txt
Download as txt, pdf, or txt
You are on page 1/ 5

Git is a software that allows you to keep track of changes made to a project ove

r time.
Git works by recording the changes you make to a project, storing those changes,
then
allowing you to reference them as needed.
We'll learn Git by using it to help us write a screenplay called Harry Programme
r and the
Sorcerer's Code.
Instructions
1. We ll get started by taking a look at the screenplay project. In scene-1.txt, add
this
text:
Harry Programmer and the Sorcerer s Code: Scene 1
Then press enter to create a new empty line. Once you've created the new line, c
lick Run.
___________________________________
Now that we have started working on the screenplay, let s turn the sorcerers-code
directory into a Git project. We do this with: git init
The word init means initialize. The command sets up all the tools Git needs to b
egin
tracking changes made to the project.
Instructions
1. In the terminal, initialize a new Git project.
Notice the output:
Initialized an empty git repository in /home/ccuser/workspace/sorcerers-code/.gi
t/
The Git project was created. Click Next to continue.
___________________________________
Nice! We have a Git project. A Git project can be thought of as having three par
ts:
A Working Directory: where you'll be doing all the work: creating, editing, dele
ting and
organizing files
A Staging Area: where you'll list changes you make to the working directory
A Repository: where Git permanently stores those changes as different versions o
f the
project
The Git workflow consists of editing files in the working directory, adding file
s to the
staging area, and saving changes to a Git repository. In Git, we save ch
anges with a
commit, which we will learn more about in this lesson.
___________________________________
As you write the screenplay, you will be changing the contents of the working di
rectory.
You can check the status of those changes with: git status
1. From the terminal, check the status of the sorcerers-code project.

In the output, notice the file in red under untracked files. Untracked means tha
t Git sees
the file but has not started tracking changes yet.
Output:
$ git status
On branch master

Initial commit

Untracked files:
(use "git add <file>..." to include in what will be committed)

scene-1.txt

nothing added to commit but untracked files present (use "git add" to track)
$
___________________________________
In order for Git to start tracking scene-1.txt, the file needs to be added to th
e staging
area.
We can add a file to the staging area with:

git add <filename>

The word <filename> here refers to the name of the file you are editing, such as
file.txt.
Instructions
1. Add scene-1.txt to the staging area in Git. Recall that you will need to iden
tify the
file by its name.
Output:
$ git add scene-1.txt
$ git status
On branch master

Initial commit

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

new file:

scene-1.txt

$
___________________________________
Good work! Now you know how to add a file to the staging area.
Imagine that we type another line in scene-1.txt. Since the file is tracked, we
can
check the differences between the working directory and the staging area with:
git diff <filename>
Instructions
1. In the code editor, add this text to scene-1.txt:
Dumblediff: I should've known you would be here, Professor McGonagit.
Click Run.
2. From the terminal, check the difference between the working directory and the
staging
area.
Notice the output:
"Harry Programmer and the Sorcerer's Code: Scene 1" is in the staging ar
ea, as
indicated in white.
Changes to the file are marked with a + and are indicated in green.
IMPORTANT: press q on your keyboard to exit diff mode.
3. Add the changes to the staging area in Git. Recall that you will need to iden
tify the
file by its name.
Output:
scene-1.txt
Harry Programmer and the Sorcerer's Code: Scene 1
Dumblediff: I should've known you would be here, Professor McGonagit.
Terminal
1 Harry Programmer and the Sorcerer's Code: Scene 1
2 Dumblediff: I should've known you would be here, Professor McGonagit.
Run
$ git status
On branch master
Initial commit
Changes to be committed:
(use "git rm --cached <file>..." to unstage)
new file:

scene-1.txt

Changes not staged for commit:


(use "git add <file>..." to update what will be committed)
(use "git checkout -- <file>..." to discard changes in working d
irectory)
modified:

scene-1.txt

$ git diff
diff --git a/scene-1.txt b/scene-1.txt
index a02a36b..597a992 100644
--- a/scene-1.txt
+++ b/scene-1.txt
@@ -1 +1,2 @@
Harry Programmer and the Sorcerer's Code: Scen
+Dumblediff: I should've known you would be her
\ No newline at end of file
(END)q
$ git add scene-1.txt
$
___________________________________
A commit is the last step in our Git workflow. A commit permanently stores chang
es from
the staging area inside the repository.
git commit is the command we'll do next. However, one more bit of code is needed
for a
commit: the option -m followed by a message.
Here's an example: git commit -m "Complete first line of dialogue"
Standard Conventions for Commit Messages:
Must be in quotation marks
Written in the present tense
Should be brief (50 characters or less) when using -m
Instructions:
Make your first commit! From the terminal, type the command along with a commit
message.
The message should describe the point of the commit.
If you're having trouble thinking of a good commit message, reflect on how the p
roject has
changed since it began.
Output:
$ git commit -m "Completed first line of dialouge"
[master (root-commit) 4c97b05] Completed first line of dialouge
1 file changed, 2 insertions(+)
create mode 100644 scene-1.txt
$
___________________________________

Often with Git, you'll need to refer back an earlier version of a project. Commi

ts are
stored chronologically in the repository and can be viewed with: git log
Instructions
1. From the terminal, log a list of your commits.
In the output, notice:
A 40-character code, called a SHA, that uniquely identifies the commit.
This appears
in orange text.
The commit author (you!)
The date and time of the commit
The commit message
Output:
$ git log
commit 4c97b05802abf9c3a359647f57a57347855a1d03
Author: codecademy <ccuser@codecademy.com>
Date:

Thu Oct 29 19:27:33 2015 -0400

Completed first line of dialouge


$
Click "Next" to continue.
FINISHED

You might also like