Fundamentals of Git By Zachary Ling 29 th, Aug, 2011 1.

Slides:



Advertisements
Similar presentations
Introduction To GIT Rob Di Marco Philly Linux Users Group July 14, 2008.
Advertisements

om om GIT - Tips & Tricks / git.dvcs git-tips.com
Hosted Git github. From an alumni (2010)  You know, the more time I spent in industry the better I've understood what a strong advocate you are for the.
Patterns & practices Symposium 2013 Introducing Git version control into your team Mark
Version Control with git. Version Control Version control is a system that records changes to a file or set of files over time so that you can recall.
1 CSE 390 “Lecture 11” Version control with Git slides created by Ruth Anderson, images from
Introduction to Git and Github Joshua imtraum.com.
BIT 285: ( Web) Application Programming Lecture 07 : Tuesday, January 27, 2015 Git.
Git for Version Control These slides are heavily based on slides created by Ruth Anderson for CSE 390a. Thanks, Ruth! images taken from
Git. What’s Git? A British swear A Distributed Version Control System Developed in 2005 by Linus Torvalds for use on the Linux Kernel Git Logo by Jason.
Introduction to Version Control with SVN & Git CSC/ECE 517, Fall 2012 Titus Barik & Ed Gehringer, with help from Gaurav.
علیرضا فراهانی استاد درس: جعفری نژاد مهر Version Control ▪Version control is a system that records changes to a file or set of files over time so.
With Mercurial and Progress.   Introduction  What is version control ?  Why use version control ?  Centralised vs. Distributed  Why Mercurial ?
Peter Ogden and Josh Levine.  Motivation  High level overview  Walk through the common operations  How not to break things (too badly)
Git – versioning and managing your software L. Grewe.
GIT An introduction to GIT Source Control. What is GIT (1 of 2) ▪ “Git is a free and open source distributed version control system designed to handle.
1 Introductory Notes on the Git Source Control Management Ric Holt, 8 Oct 2009.
Git A distributed version control system Powerpoint credited to University of PA And modified by Pepper 8-Oct-15.
ITEC 370 Lecture 16 Implementation. Review Questions? Design document on F, feedback tomorrow Midterm on F Implementation –Management (MMM) –Team roles.
Git (Get) it done right! Practical Applied Version Control for Drupal site developers Peter Chen - Stanford School of Engineering Technical Webmaster.
Version Control Systems academy.zariba.com 1. Lecture Content 1.What is Software Configuration Management? 2.Version Control Systems (VCS) 3.Basic Git.
…using Git/Tortoise Git
Git workflow and basic commands By: Anuj Sharma. Why git? Git is a distributed revision control system with an emphasis on speed, data integrity, and.
SWEN 302: AGILE METHODS Roma Klapaukh & Alex Potanin.
Team 708 – Hardwired Fusion Created by Nam Tran 2014.
Introduction to Version Control with Git CSC/ECE 517, Fall 2014 A joint project of the CSC/ECE 517 staff, including Titus Barik, Gaurav Tungatkar, Govind.
1 Applied CyberInfrastructure Concepts ISTA 420/520 Fall
By: Anuj Sharma. Topics covered:  GIT Introduction  GIT Benefits over different tools  GIT workflow  GIT server creation  How to use GIT for first.
1 GIT NOUN \’GIT\ A DISTRIBUTED REVISION CONTROL AND SOURCE CODE MANAGEMENT (SCM) SYSTEM WITH AN EMPHASIS ON SPEED. INITIALLY DESIGNED AND DEVELOPED BY.
Sofia Event Center May 2014 Martin Kulov Git For TFS Developers.
Version Control System Lisa Palathingal 03/04/2015.
GIT.
Intro to Git presented by Brian K. Vagnini Hosted by.
Falcons Git Usage Andre Pool Version 2.0 October 2015 / Veldhoven.
Introduction to Git Yonglei Tao GVSU. Version Control Systems  Also known as Source Code Management systems  Increase your productivity by allowing.
CS 160 and CMPE/SE 131 Software Engineering February 16 Class Meeting Department of Computer Science Department of Computer Engineering San José State.
Hosted Git github. From an alumnus (2010)  You know, the more time I spent in industry the better I've understood what a strong advocate you are for.
It’s not just an insult from Harry Potter!. What is Git? Distributed Version Control System (DVCS) – Compared to a Centralized Version Control System.
Introduction to Git - Chirag Dani. Objectives Basics of Git Understanding different “Mindset of Git” Demo - Git with Visual Studio.
Git How to 1. Why Git To resolve problems in lab exams (accidental deletions) Use existing Libraries with ease (Statistics and Computer) Prepare undergraduates.
BIT 285: ( Web) Application Programming Lecture 07 : Tuesday, January 27, 2015 Git.
Git A distributed version control system Powerpoint credited to University of PA And modified by Pepper 28-Jun-16.
Getting Started with Git Presented by Jim Taylor Rooty Hollow, Owner Verizon Wireless, Senior Programmer/Analyst Git User for 6 years.
Jun-Ru Chang Introduction GIT Jun-Ru Chang
Collaborative Git An introduction to Git with others
GIT Version control. Version Control Sharing code via a centralized DB Also provides for Backtracking (going back to a previous version of code), Branching.
Backing up a machine with git
KIT – University of the State of Baden-Wuerttemberg and National Research Center of the Helmholtz Association STEINBUCH CENTRE FOR COMPUTING - SCC
CS5220 Advanced Topics in Web Programming Version Control with Git
4 Version control (part 1)
Primož Gabrijelčič Git for Programmers Primož Gabrijelčič
Version Control Systems
11 Version control (part 2)
LECTURE 2: Software Configuration Management
Git Practice walkthrough.
CS5220 Advanced Topics in Web Programming Version Control with Git
Version Control System using Git
Distributed Version Control with git
Akshay Narayan git up to speed with RCS Akshay Narayan
LECTURE 3: Software Configuration Management
The Big Picture
Git CS Fall 2018.
Version control with Git
Version Control with Git and GitHub
Git Introduction.
Git GitHub.
Introduction to The Git Version Control System
Introduction To GitHub
Introduction To GitHub
Presentation transcript:

Fundamentals of Git By Zachary Ling 29 th, Aug,

Outline History of Git Distributed V.S Centralized Version Control Getting started Branching and Merging Working with remote Summary 2

A Brief History of Git Linus uses BitKeeper to manage Linux code Ran into BitKeeper licensing issue – Liked functionality – Looked at CVS as how not to do things April 5, Linus sends out showing first version June 15, Git used for Linux version control 3

Git is Not an SCM Never mind merging. It's not an SCM, it's a distribution and archival mechanism. I bet you could make a reasonable SCM on top of it, though. Another way of looking at it is to say that it's really a content-addressable filesystem, used to track directory trees. Linus Torvalds, 7 Apr

Centralized Version Control Traditional version control system – Server with database – Clients have a working version Examples – CVS – Subversion – Visual Source Safe Challenges – Multi-developer conflicts – Client/server communication 5

Distributed Version Control Authoritative server by convention only Every working checkout is a repository Get version control even when detached Backups are trivial Other distributed systems include – Mercurial – BitKeeper – Darcs – Bazaar 6

7

8

9

10

Git Advantages Resilience – No one repository has more data than any other Speed – Very fast operations compared to other VCS (I’m looking at you CVS and Subversion) Space – Compression can be done across repository not just per file – Minimizes local size as well as push/pull data transfers Simplicity – Object model is very simple Large userbase with robust tools 11

Some GIT Disadvantages Definite learning curve, especially for those used to centralized systems – Can sometimes seem overwhelming to learn Conceptual difference Huge amount of commends 12

Getting Started Git use snapshot storage 13

Getting Started Three trees of Git – The HEAD last commit snapshot, next parent – Index Proposed next commit snapshot – Working directory Sandbox 14

Getting Started A basic workflow – (Possible init or clone) Init a repo – Edit files – Stage the changes – Review your changes – Commit the changes 15

Getting Started Init a repository Git init git init Initialized empty Git repository in /home/zachary/code/gitdemo/.git/ ls -l.git/ total 32 drwxr-xr-x 2 zachary zachary :51 branches -rw-r--r-- 1 zachary zachary :51 config -rw-r--r-- 1 zachary zachary :51 description -rw-r--r-- 1 zachary zachary :51 HEAD drwxr-xr-x 2 zachary zachary :51 hooks drwxr-xr-x 2 zachary zachary :51 info drwxr-xr-x 4 zachary zachary :51 objects drwxr-xr-x 4 zachary zachary :51 refs 16

Getting Started A basic workflow – Edit files – Stage the changes – Review your changes – Commit the changes Use your favorite editor 17

Getting Started A basic workflow – Edit files – Stage the changes – Review your changes – Commit the changes Git add filename git status # On branch master # Changes not staged for commit: # (use "git add..." to update what will be committed) # (use "git checkout --..." to discard changes in working directory) # # modified: hello.txt # no changes added to commit (use "git add" and/or "git commit -a") 18

Getting Started A basic workflow – Edit files – Stage the changes – Review your changes – Commit the changes Git status git add hello.txt git status # On branch master # Changes to be committed: # (use "git reset HEAD..." to unstage) # # modified: hello.txt # 19

Getting Started A basic workflow – Edit files – Stage the changes – Review your changes – Commit the changes Git commit # Please enter the commit message for your changes. Lines starting # with '#' will be ignored, and an empty message aborts the commit. # On branch master # Changes to be committed: # (use "git reset HEAD..." to unstage) # # modified: hello.txt # 20

Getting Started A basic workflow – Edit files – Stage the changes – Review your changes – Commit the changes 21

Getting Started View changes Git diff – Show the difference between working directory and staged Git diff --cached – Show the difference between staged and the HEAD View history Git log git log commit efb3aeae e a8f52969d705d04 Author: Zachary Ling Date: Sun Aug 28 15:02: Add second line commit eae3fc5a57b e a7357 Author: Zachary Ling Date: Sun Aug 28 14:59: Initial commit 22

Getting Started Revert changes (Get back to a previous version) – Git checkout commit_hash git log commit efb3aeae e a8f52969d705d04 Author: Zachary Ling Date: Sun Aug 28 15:02: Add second line commit eae3fc5a57b e a7357 Author: Zachary Ling Date: Sun Aug 28 14:59: Initial commit git checkout 4539 Note: checking out '4539'. You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by performing another checkout. If you want to create a new branch to retain commits you create, you may do so (now or later) by using -b with the checkout command again. Example: git checkout -b new_branch_name HEAD is now at Initial commit 23

Branching Git sees commit this way… Branch annotates which commit we are working on 24

Branching 25

26

27

28

29

30

31

32

33

Merging What do we do with this mess? – Merge them 34

Merging Steps to merge two branch – Checkout the branch you want to merge onto – Merge the branch you want to merge 35

36

37

38

39

40

41

Branching and Merging Why this is cool? – Non-linear development clone the code that is in production create a branch for issue #53 (iss53) work for 10 minutes someone asks for a hotfix for issue #102 checkout ‘production’ create a branch (iss102) fix the issue checkout ‘production’, merge ‘iss102’ push ‘production’ checkout ‘iss53’ and keep working 42

Working with remote Use git clone to replicate repository Get changes with – git fetch – git pull (fetches and merges) Propagate changes with – git push Protocols – Local filesystem (file://) – SSH (ssh://) – HTTP ( – Git protocol (git://) 43

Working with remote Local filesystem Pros – Simple – Support existing access control – NFS enabled Cons – Public share is difficult to set up – Slow on top of NFS 44

Working with remote SSH Pros – Support authenticated write access – Easy to set up as most system provide ssh toolsets – Fast Compression before transfer Cons – No anonymous access Not even for read access 45

Working with remote GIT Pros – Fastest protocal – Allow public anonymous access Cons – Lack of authentication – Difficult to set up – Use port 9418 Not standard port Can be blocked 46

Working with remote HTTP/HTTPS Pros – Very easy to set up – Unlikely to be blocked Using standard port Cons – Inefficient 47

Working with remote One person project – Local repo is enough – No need to bother with remote Small team project – SSH write access for a few core developers – GIT public read access 48

Working with remote Use git remote add to add an remote repository Git remote add origin git remote origin 49

Working with remote Remote branching – Branch on remote are different from local branch 50

Working with remote Remote branching – Branch on remote are different from local branch – Git fetch origin to get remote changes – Git pull origin try to fetch reomte changes and merge it onto current branch 51

Working with remote Git push remote_name branch_name – Share your work done on branch_name to remote remote_name 52

Summary We covered fundamentals of Git – Three trees of git HEAD, INDEX and working directory – Basic work flow Modify, stage and commit cycle – Branching and merging Branch and merge – Remote Add remote, push, pull, fetch – Other commands Revert change, history view 53

Summary However, this is by no means a complete portray of git, some advanced topics are skipped: – Rebasing – Commit amend – Distributed workflow For more information, consult – Official document – Pro Git Free book available at 54

Q&A Any questions? 55

References Some of the slides are adopted from “Introduction to Git” available at files/Introduction%20To%20GIT.ppt files/Introduction%20To%20GIT.ppt Some of the figure are adopted from Pro GIT by Chacon, which is available at Some of the slides are adopted from “Git 101” available at 01%20Tutorial%20Presentation.pdf 01%20Tutorial%20Presentation.pdf 56