git in teams

Jenni Naiaretti presentation on how different teams use git to collaborate.

Transcript

1. git in teams Jenni Naiaretti | forLoop
2. the team • Solo • Strangers • Colleagues
3. why git? Maintain back ups Stage your growth Create versions Remote access Neat experiments Multitask Mix and match Keep records
4. workflows • Centralised • Feature branch • GitFlow • Forking
5. centralised * git is a distributed vcs and encourages collaboration One main upstream branch 1..* local branches Merges are paced
6. feature branch Commits for a feature are in one branch Branch naming convention {<feature-x> != developer-a} Master is official Parent node of every branch Branches stay in sync Merge when done Review finished work Spot drastic changes Delete after merging
7. gitflow Feature + extra branching Production/stable branch master Development branch dev Feature branches Release branches Hotfix branches
8. MASTER BRANCH No direct pushes Tag all merges; annotate Update master through release/hotfix branches DEV BRANCH master -> dev Stay in sync with master Should ideally be stable, cover with tests gitflow
9. FEATURE BRANCHES Based off of dev NOT master master -> dev <-> feature RELEASE BRANCH Test & fix bugs* Change log & Documentation Version product (tag number) master <- release <-> dev <-> feature gitflow
10. HOTFIX BRANCH dev not ready but master can’t wait Create from master master <-> hotfix -> release <-> dev <-> feature master <-> hotfix -> dev <-> feature gitflow
11. Omnipresent repository Track upstream remote git remote add upstream repo.git Git pull upstream stable/master My forked repo: me@host forking
12. Pushes are restricted to project owner(s) Tag, you’re it! Share one fork - third party project Multiple forks per member: in-house Dependency CI forking
13. Merging Pull request <me@host feature> → <upstream stable/master> Upstream accepts Fix conflicts and test locally Fetch <me@host feature> git merge FETCH_HEAD forking
14. damage control • Pass the test • Grep • Ctrl+Z • Bisect • Blame someone
15. debugging Git is not God Test stable/master branch GREP Search for a pattern View the file lines/name *Rollback a release or checkout a working revision
16. the good, the bad, the broken BISECT Initiate a bisect investigation Specify the bad and the good revisions Test manually or run a test script Locate where the problem was introduced git bisect start git bisect bad git bisect good [<rev>] git bisect reset
17. it was working yesterday! You can blame CLI or Toolkits shipped with git {gitk} Clients Git services It’s all in the setup Use coding conventions to avoid false accusations Understand before you change Who should merge
18. people & projects • Security • Access management • Identities
19. security & access Don’t track sensitive info Team-defined standards Configurations: personal + team defined rm is not enough Branch restriction/protection Alerts
20. tips Init & update all submodules in repo Git clone -- recursive repo.git See more detail by adding -p to most commands Stay on top of stashes with meaningful messages git add can/accept multiple.files *.twig git clean -n instead of rm-ing each file Git GUI Clients https://git-scm.com/download/gui/linux
21. useful resources Cheat sheet: http://ndpsoftware.com/git-cheatsheet.html Damage control flowchart: http://justinhileman.info/article/git-pretty/git-pretty.png Getting git right: https://www.atlassian.com/git/ GitHub git cheat sheet: https://services.github.com/kit/downloads/github-git-cheat-sheet.pdf GitHub help: https://help.github.com/ Git SCM: https://git-scm.com How to: https://githowto.com/setup How to use git & GitHub: https://www.udacity.com/course/how-to-use-git-and-github--ud775 Learn git on the browser: https://www.codeschool.com/courses/try-git