## Let's git going - A little bit of background (45m) - Why version control, why Git? - Nitty-gritty Git - Ready, set ... - prerequisites (10m) - ☕ - go - hands on

## Why version control?

## Why Git? >Indeed, the ratio of time spent reading versus writing is well over 10 to 1. We are constantly reading old code as part of the effort to write new code. Making it easy to read makes it easier to write. (Robert C. Martin)

- [70% of the worlds code](https://www.openhub.net/repositories/compare) and growing - faster ( offline ) - better algorithms - matches agile way of working ( ie feature branches)

## Git concepts

## change set - leaves the repo in consistent state - author - commit message

## block chain - cryptographic hash - block chain - commit tree

## distributed - all important workflows are local - can have multiple remotes

## Prerequisites [Find them](https://github.com/baloise/HelloGit/wiki/Prerequisites) in the wiki

## git commmands http://www.ndpsoftware.com/git-cheatsheet.html

## go go git ... [hands on](https://github.com/baloise/HelloGit/wiki/Local-Git)

## advanced topics ... AKA _things we don't do_ - stash - rebase

## integration - github - bitbucket / jenkins - fork/pull vs branch/merge

## clients - [git bash](https://git-scm.com/downloads) - [TortoiseGit](https://tortoisegit.org/download/) - [Sourcetree](https://www.sourcetreeapp.com/) - [Visual Studio Code](https://code.visualstudio.com/download) - [Eclipse](https://www.eclipse.org/downloads/) - [ungit](https://github.com/FredrikNoren/ungit/releases) - https://dillinger.io/

## hand outs & further reading - hand outs - https://github.com/AlexZeitler/gitcheatsheet - assets/img/handout2.svg - further reading - https://git-scm.com/book/ - https://www.atlassian.com/git

Did you know that this presentation is also managed in git? You can easily contribute under https://github.com/baloise/reveal.js/blob/letsGitGoing/index.html  To the extent possible under law, the person who associated CC0 with this work has waived all copyright and related or neighboring rights to this work. Not sure what license to pick for your own project? Check out the [licensing section of the Baloise Open Source Guidelines](https://baloise.github.io/open-source/docs/arc42/#section-licenses).