Your browser doesn't support the features required by impress.js, so you are presented with a simplified version of this presentation.

For the best experience please use the latest Chrome, Safari or Firefox browser.

\[._.]/ - Oh, Hi!

I'm Adam Eivy (@antic)

Solutions Engineering Architect, Disney
Occasional Web Development Instructor, SCCC

Let's talk about Version Control Systems (VCS)...

This is complicated...

Step 1: Melt Your Brains (Overview)
Step 2: Try Some Hands On Git
Step 3: Push You Out of the Nest

Why?

Centralizing Code

Collaboration


It isn't always easy.



History

Looking up code history can answer a lot of questions about how code got where it is:

Branching

A little later, we'll go over Git Flow to see how this works

Methods

some flawed attempts*

Some actual versioning tools*

* list goes on and on (Hg, Perforce, CVS, Bridge...)

File Renaming

(index.html, index_2.html, index_3.html, index_adam_2.html)

Dreamweaver

ಠ_ಠ

Subversion (SVN)

Git

GitHub

Process

Check in frequently

  1. Commit locally
    git commit -m 'added some stuff'
  2. Rebase to wrap-up changes
    git rebase
  3. Push it out
    git push
  4. Bask in awesomeness
    \[._.]/

Merge Conflict!

Clean

Raw Merge

Araxis

Code Review

Fork and Pull Request

If you do this, you rock!

What now?



Code School


http://try.github.com

Markdown

Create a README.md file in every project!


http://daringfireball.net/projects/markdown

Command Line

Learn it
Use it
<3 it

Free Ebook: Pro Git


http://git-scm.com/book/

Questions?



Slide Viewable on Github:

http://atomantic.github.io/slides-versioncontrol

p.s. check out A.D.D.

Adam Eivy (@antic)

adam.eivy@disney.com
Solutions Engineering Architect
Disney Technology Solutions and Services

Use a spacebar or arrow keys to navigate