Mais conteúdo relacionado
Semelhante a Git in the Van HighEdWeb 2013 (20)
Git in the Van HighEdWeb 2013
- 4. “When you work within your
confines, when you realize
your limitations, that’s when
you can break through them.”!
- 8. Why Choose Git?
• Open Source (free)
• Distributed gives you autonomy
• Easy branching for experimenting
- 10. The Δ
It’s Efficient
• Revisions, not versions
• Repo stores all changes
– 1st
change:
git init!
• Each change links to previous
- 15. Step 1:
All the Things!
• Take some shirts out of the closet
• Throw them on the bed
- 22. Step 1
• Take pants out of the closet
• Touched the pants – that’s an edit
• The pants are in your working copy
- 24. Step 2
• Choose a few pants, fold them up
• Selected a change – that’s an add
• The pants are in your staging index
- 26. Step 3
• Put the folded pants in your suitcase
• Packed the pants – that’s a commit
• The pants are in your repo
- 29. Step 1
• Take socks out of the drawer
• COMMAND: (none)
– Git
compares
current
files
to
repo
– Changes
go
in
working
copy
automatically
- 31. Step 2
• Pick a few socks, roll them up
• COMMAND: git add
– Moves changes to staging index
– Works for edited files or new files
- 33. Step 3
• Pack the socks in your suitcase
• COMMAND: git commit
– Records the changes to your repo
– Can be a single change or many
- 35. Step 4
• Put unused clothes away
• COMMAND: git checkout
– Erases changes from the working copy
– A good way to get out of a bad situation
- 52. Get a Passport
• A new item, not yet tracked
• COMMAND: git add
– Skip the working copy
– Add directly to staging index
!
- 56. Merge the Changes
• Add the change to the master
branch
• COMMAND: git merge
– Merge all changes or cherry pick
- 63. Credits
• Quotes from Get in the Van
by Henry Rollins
• Designer:
Jacob
Melton
meltonjd@dukes.jmu.edu
• Presenter:
Annette
Liskey
liskeyab@jmu.edu
