23
It's time to talk about Git and the importance of source control!

Using Git on the Command Line

Embed Size (px)

Citation preview

Page 1: Using Git on the Command Line

It's time to talk about Git and the importance of

source control!

Page 2: Using Git on the Command Line

Imagine a scenario, if you will...

Page 3: Using Git on the Command Line

You've uploaded a broken file, you don't have a working copy.

What do you do?

Page 4: Using Git on the Command Line

Git to the rescue!

Page 5: Using Git on the Command Line

Revert the file, upload it again, and life is great!

Page 6: Using Git on the Command Line

Wow! How does Git work?

Page 7: Using Git on the Command Line
Page 8: Using Git on the Command Line
Page 9: Using Git on the Command Line
Page 10: Using Git on the Command Line

Sounds great, but how do we use Git?

Page 11: Using Git on the Command Line

If you're intimidated by the command line, I recommend SourceTree:

Page 12: Using Git on the Command Line

But I promise, using git on the command line is

really easy!

Page 13: Using Git on the Command Line

Creating a new repository is as easy as typing:

$ git init

This adds the basic structures Git needs in order to function properly

Page 14: Using Git on the Command Line

Cloning an existing repository is just as easy:

$ git clone <repo url>

This pulls down the entire git history for a given project and lets you manipulate

it as if you had created it.

Page 15: Using Git on the Command Line

Adding files to your repository:

$ git add *

This will add ALL files in the current directory to your repository.

Page 16: Using Git on the Command Line

Committing a set of changes:

$ git commit -m "My commit message"

This will save all staged changes to a reference point you can always restore.

Page 17: Using Git on the Command Line

Checking a repository's status

$ git status

This reports which files have been modified, added, removed, etc.

Page 18: Using Git on the Command Line

Un-staging some edited files:

$ git reset

This returns all staged files back to being unstaged. It does NOT undo any

edits to those files by default.

Page 19: Using Git on the Command Line

Temporarily store staged edits:

$ git stash

Think of this as a way of saying, "I'm not ready to do anything with these edits,

but I don't want to erase them."

Page 20: Using Git on the Command Line

Start a new "branch" for tracking edits: $ git branch mybranch

We'll use this separate branch to develop a new feature, safely isolated

from the main codebase and bug fixes.

$ git checkout -b mybranch

–or–

Page 21: Using Git on the Command Line

Merge a branch back into master: $ git checkout master $ git merge mybranch

First we switch back to the master branch, then we merge in all changes

from mybranch.

Page 22: Using Git on the Command Line

Pushing Edits to a remote server:

$ git push

Yep, that's really all there is to it!

Page 23: Using Git on the Command Line

Any Questions?