Chances are good that you've heard about Git, the distributed source control system that's taking the development world by storm. Organizations of all sizes are taking the plunge, and InCycle is here to help you make the transition smooth and easy. This webcast will present an overview of the Git source control model and compare it to other source control solutions like Team Foundation Version Control and Subversion, so you can understand the key differences between them and what all the buzz is about!
Mcleodganj Call Girls 🥰 8617370543 Service Offer VIP Hot Model
Introduction to Git
1. Introduction to Git
Daniel Mann
Senior Software DevelopmentConsultant
InCycle Software
NewYork ▪ Seattle ▪ Montreal
2. Agenda
What is Git?
Overview of Centralized vs Distributed Version Control
Git in Visual Studio / TFS
Is It Right For Me?
3. What is Git?
- Distributed version control system
- Designed for the challenges of large-scale open-
source projects
- Supports fast, off-line work
4. Centralized Version Control
One central code repository
Requires a connection to perform most operations
Check out
Commit
Merge
Branch
View History
Can retrieve just the files you need
Limited capability for offline work
Conceptually simple
5. Distributed Version Control
No central code repository
Central repository is defined by convention
Does not require a connection
Can only retrieve an entire repository
Higher learning curve
10. Distributed Version Control
PC 1
Repository
Remote Server
Repo
Pull Remote Changes
Change 1
Change 2
Change 3
Change 1
Change 2
My Change
Change 3
Change 1
Change 2
My Change
Change 3
11. Distributed Version Control
PC 1
Repository
Remote Server
Repo
Merge remote changes
with local changesChange 1
Change 2
My Change
Change 3
Change 1
Change 2
Change 3
Change 1
Change 2
My Change
Change 3
Change 4
12. Distributed Version Control
PC 1
Repository
Remote Server
Repo
Change 1
Change 2
Change 3
Change 1
Change 2
My Change
Change 3
Change 4
Push Local Changes
My Change
Change 4
Change 1
Change 2
My Change
Change 3
Change 4
13. Why Distributed?
Work fully offline
Encourages frequent commits
Easy to switch work
Powerful tools for viewing and rewriting history
Increasingly popular
14. Why Not Distributed?
Harder to use day-to-day
Few non-OSS projects need the ability to rewrite
history
Git does not handle binaries well
Security is defined at the repository level
15. Git in Visual Studio
Works regardless
of your Git provider
…even against local repos.
30. Should you make the switch?
Yes, if:
- You work offline frequently
- Your software is open-source
- You want to branch and merge frequently
31. Should you make the switch?
No, if:
- You never work offline
- Your software is closed-source
- Developers are productive and happy using
something else
- You require stringent code security
32. Best Practices
Don’t Panic
Do not put binaries in Git repositories!
Manage binary dependencies via a package
manager
Keep repos small (one repo == one application)
Branch early, branch often. Don’t work directly on
master.
Read the Docs!
33. /InCycleSoftware @InCycleSoftware /company/incycle-software incyclesoftware.com/blog/
Get started with Git!
For course/workshops overviews, see links below:
Course: Git Fundamentals–
http://incyclesoftware.com/course-git-fundamentals/
Course: Git in Team Foundation Server & VisualStudio -
http://incyclesoftware.com/course-git-in-team-foundation-server-visual-studio/
Workshop: Git Migration–
http://incyclesoftware.com/workshop-git-migration/
Toschedule a courseor workshop, emailus atinfo@incyclesoftware.com or call1-800-565-0510