git

$ git init

Git Clone Recap

The git clone command is used to create an identical copy of an existing repository.

$ git clone <path-to-repository-to-clone>

This command:

• takes the path to an existing repository
• by default will create a directory with the same name as the repository that’s being cloned
• can be given a second argument that will be used as the name of the directory
• will create the new repository inside of the current working directory

Helpful Links

• Cloning an Existing Repository
• git clone docs
• git clone Tutorial

Git Status Recap

The git status command will display the current status of the repository.

$ git status

I can’t stress enough how important it is to use this command all the time as you’re first learning Git. This command will:

• tell us about new files that have been created in the Working Directory that Git hasn’t started tracking, yet
• files that Git is tracking that have been modified
• a whole bunch of other things that we’ll be learning about throughout the rest of the course 😉

Git Log Recap

Fantastic job! Do you feel your Git-power growing?

Let’s do a quick recap of the git log command. The git log command is used to display all of the commits of a repository.

$ git log

By default, this command displays:

• the SHA
• the author
• the date
• and the message

…of every commit in the repository. I stress the “By default” part of what Git displays because the git log command can display a lot more information than just this.

Git uses the command line pager, Less, to page through all of the information. The important keys for Less are:

• to scroll down by a line, use j or ↓
• to scroll up by a line, use k or ↑
• to scroll down by a page, use the spacebar or the Page Down button
• to scroll up by a page, use b or the Page Up button
• to quit, use q

We’ll increase our git log-wielding abilities in the next lesson when we look at displaying more info.

git log –oneline Recap

To recap, the --oneline flag is used to alter how git log displays information:

$ git log --oneline

This command:

• lists one commit per line
• shows the first 7 characters of the commit’s SHA
• shows the commit’s message

git log --stat Recap

To recap, the --stat flag is used to alter how git log displays information:

$ git log --stat

This command:

• displays the file(s) that have been modified
• displays the number of lines that have been added/removed
• displays a summary line with the total number of modified files and lines that have been added/removed

git log -p Recap

To recap, the -p flag (which is the same as the --patch flag) is used to alter how git log displays information:

$ git log -p

This command adds the following to the default output:

• displays the files that have been modified
• displays the location of the lines that have been added/removed
• displays the actual changes that have been made

$ git log -p fdf5493

$ git show

$ git show fdf5493

Git Add Recap

The git add command is used to move files from the Working Directory to the Staging Index.

$ git add <file1> <file2> … <fileN>

This command:

• takes a space-separated list of file names
• alternatively, the period . can be used in place of a list of files to tell Git to add the current directory (and all nested files)

Git Commit Recap

The git commit command takes files from the Staging Index and saves them in the repository.

$ git commit

This command:

• will open the code editor that is specified in your configuration
  • (check out the Git configuration step from the first lesson to configure your editor)

Inside the code editor:

• a commit message must be supplied
• lines that start with a # are comments and will not be recorded
• save the file after adding a commit message
• close the editor to make the commit

Then, use git log to review the commit you just made!

Git Diff Recap

To recap, the git diff command is used to see changes that have been made but haven’t been committed, yet:

$ git diff

This command displays:

• the files that have been modified
• the location of the lines that have been added/removed
• the actual changes that have been made

Further Research

• git diff from the Git Docs

Git Ignore Recap

To recap, the .gitignore file is used to tell Git about the files that Git should not track. This file should be placed in the same directory that the .git directory is in.

Further Research

• Ignoring files from the Git Book
• gitignore from the Git Docs
• Ignoring files from the GitHub Docs
• gitignore.io

Git Tag Recap

To recap, the git tag command is used to add a marker on a specific commit. The tag does not move around as new commits are added.

$ git tag -a beta

This command will:

• add a tag to the most recent commit
• add a tag to a specific commit if a SHA is passed

Further Research

• Git Basics – Tagging from the Git Book
• Git Tag from the Git Docs

Git Branch Recap

To recap, the git branch command is used to manage branches in Git:

# to list all branches
$ git branch

# to create a new "footer-fix" branch
$ git branch footer-fix

# to delete the "footer-fix" branch
$ git branch -d footer-fix

This command is used to:

• list out local branches
• create new branches
• remove branches

Further Research

• Git Branching – Basic Branching and Merging from the Git Docs
• Learn Git Branching
• Git Branching Tutorial from the Atlassian Blog

…

…

…

Expand On Your Git Skills

• take the companion GitHub course
• create a repo to track your computer’s settings – https://dotfiles.github.io/
• develop the next, awesome feature for your personal project
• try tackling some Git challenges with the Git-it app

GITHUB

Quick setup — if you’ve done this kind of thing before

echo "# test" >> README.md
git init
git add README.md
git commit -m "first commit"
git remote add origin https://github.com/thomasdmtang/test.git
git push -u origin master

git remote add origin https://github.com/thomasdmtang/test.git
git push -u origin master